From: claudio.fontana@huawei•com (Claudio Fontana)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH 3/3] KVM: ARM: Update documentation for KVM_ARM_VCPU_INIT ioctl
Date: Fri, 6 Sep 2013 10:05:11 +0200 [thread overview]
Message-ID: <52298CB7.6060501@huawei.com> (raw)
In-Reply-To: <1378392362-6773-4-git-send-email-anup.patel@linaro.org>
Hi Anup,
I am no native English speaker, but this is my attempt at improving the descriptions:
On 05.09.2013 16:46, Anup Patel wrote:
> To implement target type KVM_ARM_TARGET_HOST we make the
> KVM_ARM_VCPU_INIT ioctl bi-direction so that KVM ARM/ARM64
> can return appropriate target type to user space via
> struct kvm_vcpu_init.
If I understood correctly:
To implement target type KVM_ARM_TARGET_HOST we change
the "struct kvm_cpu_init" input parameter into an in/out
parameter, so that KVM ARM/ARM64 can inform user space about
the chosen target type.
> Signed-off-by: Anup Patel <anup.patel@linaro•org>
> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro•org>
> ---
> Documentation/virtual/kvm/api.txt | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
> index ef925ea..c0a3a05 100644
> --- a/Documentation/virtual/kvm/api.txt
> +++ b/Documentation/virtual/kvm/api.txt
> @@ -2283,7 +2283,7 @@ current state. "addr" is ignored.
> Capability: basic
> Architectures: arm, arm64
> Type: vcpu ioctl
> -Parameters: struct struct kvm_vcpu_init (in)
> +Parameters: struct kvm_vcpu_init (in/out)
> Returns: 0 on success; -1 on error
> Errors:
> EINVAL: the target is unknown, or the combination of features is invalid.
> @@ -2303,6 +2303,9 @@ Possible features:
> - KVM_ARM_VCPU_EL1_32BIT: Starts the CPU in a 32bit mode.
> Depends on KVM_CAP_ARM_EL1_32BIT (arm64 only).
>
> +This ioctl returns updated struct kvm_vcpu_init showing VCPU target
> +type and VCPU features that will be available.
> +
This ioctl returns an updated struct kvm_vcpu_init informing about the
chosen VCPU target type and available VCPU features.
>
> 4.83 KVM_GET_REG_LIST
>
>
Ciao,
Claudio
next prev parent reply other threads:[~2013-09-06 8:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 14:45 [RFC PATCH 0/3] Target CPU=Host implementation for KVM ARM/ARM64 Anup Patel
2013-09-05 14:46 ` [RFC PATCH 1/3] ARM: KVM: Implement target CPU=Host Anup Patel
2013-09-06 8:08 ` Claudio Fontana
2013-09-05 14:46 ` [RFC PATCH 2/3] ARM64: " Anup Patel
2013-09-06 8:09 ` Claudio Fontana
2013-09-05 14:46 ` [RFC PATCH 3/3] KVM: ARM: Update documentation for KVM_ARM_VCPU_INIT ioctl Anup Patel
2013-09-06 8:05 ` Claudio Fontana [this message]
2013-09-06 10:13 ` Anup Patel
2013-09-05 14:51 ` [RFC PATCH 0/3] Target CPU=Host implementation for KVM ARM/ARM64 Peter Maydell
2013-09-06 7:44 ` Anup Patel
2013-09-06 8:54 ` Alexander Graf
2013-09-06 9:06 ` Will Deacon
2013-09-06 10:09 ` Anup Patel
2013-09-06 10:49 ` Will Deacon
2013-09-06 10:51 ` Anup Patel
2013-09-06 10:52 ` Will Deacon
2013-09-06 10:05 ` Anup Patel
2013-09-06 10:24 ` Alexander Graf
2013-09-06 10:34 ` Marc Zyngier
2013-09-06 10:38 ` Anup Patel
2013-09-06 10:34 ` Anup Patel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52298CB7.6060501@huawei.com \
--to=claudio.fontana@huawei$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox