From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Jonathan Corbet" <corbet@lwn.net>,
kvm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] doc: kvm: Fix return description of KVM_SET_MSRS
Date: Thu, 5 Sep 2019 09:11:53 +0800 [thread overview]
Message-ID: <5e61463e-b389-4393-81f9-a154ee4688be@intel.com> (raw)
In-Reply-To: <20190904174122.GK24079@linux.intel.com>
On 9/5/2019 1:41 AM, Sean Christopherson wrote:
> On Wed, Sep 04, 2019 at 02:01:18PM +0800, Xiaoyao Li wrote:
>> Userspace can use ioctl KVM_SET_MSRS to update a set of MSRs of guest.
>> This ioctl sets specified MSRs one by one. Once it fails to set an MSR
>> due to setting reserved bits, the MSR is not supported/emulated by kvm,
>> or violating other restrictions, it stops further processing and returns
>> the number of MSRs have been set successfully.
>>
>> Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
>> ---
>> v2:
>> elaborate the changelog and description of ioctl KVM_SET_MSRS based on
>> Sean's comments.
>>
>> ---
>> Documentation/virt/kvm/api.txt | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/virt/kvm/api.txt b/Documentation/virt/kvm/api.txt
>> index 2d067767b617..4638e893dec0 100644
>> --- a/Documentation/virt/kvm/api.txt
>> +++ b/Documentation/virt/kvm/api.txt
>> @@ -586,7 +586,7 @@ Capability: basic
>> Architectures: x86
>> Type: vcpu ioctl
>> Parameters: struct kvm_msrs (in)
>> -Returns: 0 on success, -1 on error
>> +Returns: number of msrs successfully set (see below), -1 on error
>>
>> Writes model-specific registers to the vcpu. See KVM_GET_MSRS for the
>> data structures.
>> @@ -595,6 +595,11 @@ Application code should set the 'nmsrs' member (which indicates the
>> size of the entries array), and the 'index' and 'data' members of each
>> array entry.
>>
>> +It tries to set the MSRs in array entries[] one by one. Once failing to
>
> Probably better to say 'If' as opposed to 'Once', don't want to imply that
> userspace is incompetent :)
>
>> +set an MSR (due to setting reserved bits, the MSR is not supported/emulated
>> +by kvm, or violating other restrctions),
>
> Make it clear the list is not exhaustive, e.g.:
>
> It tries to set the MSRs in array entries[] one by one. If setting an MSR
> fails, e.g. due to setting reserved bits, the MSR isn't supported/emulated by
> KVM, etc..., it stops processing the MSR list and returns the number of MSRs
> that have been set successfully.
>
Refine it as you commented and send out v3, thanks.
>> it stops setting following MSRs
>> +and returns the number of MSRs have been set successfully.
>> +
>>
>> 4.20 KVM_SET_CPUID
>>
>> --
>> 2.19.1
>>
prev parent reply other threads:[~2019-09-05 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 6:01 Xiaoyao Li
2019-09-04 17:41 ` Sean Christopherson
2019-09-05 1:11 ` Xiaoyao Li [this message]
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=5e61463e-b389-4393-81f9-a154ee4688be@intel.com \
--to=xiaoyao.li@intel.com \
--cc=corbet@lwn.net \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
all inboxes | Powered by JetHome®