From: Paolo Bonzini <pbonzini@redhat.com>
To: "Sean Christopherson" <sean.j.christopherson@intel.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: VMX: Fix and tweak the comments for VM-Enter
Date: Mon, 19 Aug 2019 17:47:33 +0200 [thread overview]
Message-ID: <aa33f0e1-e999-08b0-8826-0b88f4681561@redhat.com> (raw)
In-Reply-To: <20190815200931.18260-1-sean.j.christopherson@intel.com>
On 15/08/19 22:09, Sean Christopherson wrote:
> Fix an incorrect/stale comment regarding the vmx_vcpu pointer, as guest
> registers are now loaded using a direct pointer to the start of the
> register array.
>
> Opportunistically add a comment to document why the vmx_vcpu pointer is
> needed, its consumption via 'call vmx_update_host_rsp' is rather subtle.
>
> Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
> ---
> arch/x86/kvm/vmx/vmenter.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx/vmenter.S b/arch/x86/kvm/vmx/vmenter.S
> index 4010d519eb8c..751a384c2eb0 100644
> --- a/arch/x86/kvm/vmx/vmenter.S
> +++ b/arch/x86/kvm/vmx/vmenter.S
> @@ -94,7 +94,7 @@ ENDPROC(vmx_vmexit)
>
> /**
> * __vmx_vcpu_run - Run a vCPU via a transition to VMX guest mode
> - * @vmx: struct vcpu_vmx *
> + * @vmx: struct vcpu_vmx * (forwarded to vmx_update_host_rsp)
> * @regs: unsigned long * (to guest registers)
> * @launched: %true if the VMCS has been launched
> *
> @@ -151,7 +151,7 @@ ENTRY(__vmx_vcpu_run)
> mov VCPU_R14(%_ASM_AX), %r14
> mov VCPU_R15(%_ASM_AX), %r15
> #endif
> - /* Load guest RAX. This kills the vmx_vcpu pointer! */
> + /* Load guest RAX. This kills the @regs pointer! */
> mov VCPU_RAX(%_ASM_AX), %_ASM_AX
>
> /* Enter guest mode */
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2019-08-19 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 20:09 Sean Christopherson
2019-08-16 18:22 ` Jim Mattson
2019-08-19 15:47 ` 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=aa33f0e1-e999-08b0-8826-0b88f4681561@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®