From: Gleb Natapov <gleb@redhat.com>
To: Arthur Chunqi Li <yzt356@gmail.com>
Cc: kvm <kvm@vger.kernel.org>, "Ren, Yongjie" <yongjie.ren@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] KVM: nVMX: correctly set tr base on nested vmexit emulation
Date: Sun, 4 Aug 2013 15:59:56 +0300 [thread overview]
Message-ID: <20130804125956.GP6042@redhat.com> (raw)
In-Reply-To: <CABpY8M+QM+VERJkCnEzFt+DZCjNqUA1g8iFRo2DdSQadUswxOw@mail.gmail.com>
On Sun, Aug 04, 2013 at 08:21:00PM +0800, Arthur Chunqi Li wrote:
> Yes, I have just retraced and found the bug. This is my negligence.
>
Reviewers could have done a better job too :)
> Reviewed-by: Arthur Chunqi Li <yzt356@gmail.com>
>
> On Sun, Aug 4, 2013 at 8:08 PM, Gleb Natapov <gleb@redhat.com> wrote:
> > After commit 21feb4eb64e21f8dc91136b91ee886b978ce6421 tr base is zeroed
> > during vmexit. Set it to L1's HOST_TR_BASE. This should fix
> > https://bugzilla.kernel.org/show_bug.cgi?id=60679
> >
> > Signed-off-by: Gleb Natapov <gleb@redhat.com>
> > diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> > index b533cf8..7d31e7b 100644
> > --- a/arch/x86/kvm/vmx.c
> > +++ b/arch/x86/kvm/vmx.c
> > @@ -8261,7 +8261,7 @@ static void load_vmcs12_host_state(struct kvm_vcpu *vcpu,
> > seg.base = vmcs12->host_gs_base;
> > vmx_set_segment(vcpu, &seg, VCPU_SREG_GS);
> > seg = (struct kvm_segment) {
> > - .base = 0,
> > + .base = vmcs12->host_tr_base,
> > .limit = 0x67,
> > .selector = vmcs12->host_tr_selector,
> > .type = 11,
> > --
> > Gleb.
>
>
>
> --
> Arthur Chunqi Li
> Department of Computer Science
> School of EECS
> Peking University
> Beijing, China
--
Gleb.
next prev parent reply other threads:[~2013-08-04 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 12:08 [PATCH] KVM: nVMX: correctly set tr base on nested vmexit emulation Gleb Natapov
2013-08-04 12:21 ` Arthur Chunqi Li
2013-08-04 12:59 ` Gleb Natapov [this message]
2013-08-05 6:23 ` Ren, Yongjie
2013-08-07 14:07 ` Paolo Bonzini
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=20130804125956.GP6042@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=yongjie.ren@intel.com \
--cc=yzt356@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.