From: Paolo Bonzini <pbonzini@redhat.com>
To: linmiaohe <linmiaohe@huawei.com>,
rkrcmar@redhat.com, sean.j.christopherson@intel.com,
vkuznets@redhat.com, wanpengli@tencent.com, jmattson@google.com,
joro@8bytes.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] KVM: nVMX: Fix some obsolete comments and grammar error
Date: Fri, 14 Feb 2020 10:00:09 +0100 [thread overview]
Message-ID: <4fdb28f3-dbaa-34bb-2da4-496ca881fb2a@redhat.com> (raw)
In-Reply-To: <1581648245-8414-1-git-send-email-linmiaohe@huawei.com>
On 14/02/20 03:44, linmiaohe wrote:
> From: Miaohe Lin <linmiaohe@huawei.com>
>
> Fix wrong variable names and grammar error in comment.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> arch/x86/kvm/vmx/nested.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
> index 657c2eda357c..f2d8cb68dce8 100644
> --- a/arch/x86/kvm/vmx/nested.c
> +++ b/arch/x86/kvm/vmx/nested.c
> @@ -3160,10 +3160,10 @@ static void load_vmcs12_host_state(struct kvm_vcpu *vcpu,
> * or KVM_SET_NESTED_STATE). Otherwise it's called from vmlaunch/vmresume.
> *
> * Returns:
> - * NVMX_ENTRY_SUCCESS: Entered VMX non-root mode
> - * NVMX_ENTRY_VMFAIL: Consistency check VMFail
> - * NVMX_ENTRY_VMEXIT: Consistency check VMExit
> - * NVMX_ENTRY_KVM_INTERNAL_ERROR: KVM internal error
> + * NVMX_VMENTRY_SUCCESS: Entered VMX non-root mode
> + * NVMX_VMENTRY_VMFAIL: Consistency check VMFail
> + * NVMX_VMENTRY_VMEXIT: Consistency check VMExit
> + * NVMX_VMENTRY_KVM_INTERNAL_ERROR: KVM internal error
> */
> enum nvmx_vmentry_status nested_vmx_enter_non_root_mode(struct kvm_vcpu *vcpu,
> bool from_vmentry)
> @@ -5301,7 +5301,7 @@ static bool nested_vmx_exit_handled_io(struct kvm_vcpu *vcpu,
> }
>
> /*
> - * Return 1 if we should exit from L2 to L1 to handle an MSR access access,
> + * Return 1 if we should exit from L2 to L1 to handle an MSR access,
> * rather than handle it ourselves in L0. I.e., check whether L1 expressed
> * disinterest in the current event (read or write a specific MSR) by using an
> * MSR bitmap. This may be the case even when L0 doesn't use MSR bitmaps.
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-02-14 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 2:44 linmiaohe
2020-02-14 9:00 ` Paolo Bonzini [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=4fdb28f3-dbaa-34bb-2da4-496ca881fb2a@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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®