From: Avi Kivity <avi@redhat.com>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: MMU: Do not unconditionally read PDPTE from guest memory
Date: Tue, 02 Aug 2011 15:34:32 +0300 [thread overview]
Message-ID: <4E37EED8.6030203@redhat.com> (raw)
In-Reply-To: <20110802093109.GP5176@amd.com>
On 08/02/2011 12:31 PM, Roedel, Joerg wrote:
> On Sun, Jul 31, 2011 at 04:08:44AM -0400, Avi Kivity wrote:
> > On 07/29/2011 02:31 PM, Roedel, Joerg wrote:
> > > On Thu, Jul 28, 2011 at 04:36:17AM -0400, Avi Kivity wrote:
> > > > Architecturally, PDPTEs are cached in the PDPTRs when CR3 is reloaded.
> > > > On SVM, it is not possible to implement this, but on VMX this is possible
> > > > and was indeed implemented until nested SVM changed this to unconditionally
> > > > read PDPTEs dynamically. This has noticable impact when running PAE guests.
> > > >
> > > > Fix by changing the MMU to read PDPTRs from the cache, falling back to
> > > > reading from memory for the nested MMU.
> > > >
> > > > Signed-off-by: Avi Kivity<avi@redhat.com>
> > >
> > > Hmm, interesting. Sorry for breaking it. I tested the patch on nested
> > > svm, it works fine.
> >
> > Does pae-on-pae work for you?
>
> Only tested pae-on-longmode. I'll see if I can find my 32bit
> installation again and test this too.
I wanted to test it since any mixup in where the PTPTRs were taken from
would be readily apparent. But it crashes even without the patch.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-08-02 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 8:36 [PATCH] KVM: MMU: Do not unconditionally read PDPTE from guest memory Avi Kivity
2011-07-29 11:31 ` Roedel, Joerg
2011-07-31 8:08 ` Avi Kivity
2011-08-02 9:31 ` Roedel, Joerg
2011-08-02 12:34 ` Avi Kivity [this message]
2011-08-02 13:11 ` Roedel, Joerg
2011-08-04 9:49 ` Roedel, Joerg
2011-08-05 15:14 ` Marcelo Tosatti
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=4E37EED8.6030203@redhat.com \
--to=avi@redhat.com \
--cc=Joerg.Roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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.