From: Gleb Natapov <gleb@redhat.com>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Cc: markus@trippelsdorf.de, mtosatti@redhat.com, pbonzini@redhat.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: MMU: avoid fast page fault fixing mmio page fault
Date: Thu, 18 Jul 2013 09:06:28 +0300 [thread overview]
Message-ID: <20130718060628.GA15613@redhat.com> (raw)
In-Reply-To: <51E784CB.1040402@linux.vnet.ibm.com>
On Thu, Jul 18, 2013 at 02:01:47PM +0800, Xiao Guangrong wrote:
> On 07/18/2013 01:31 PM, Gleb Natapov wrote:
> > On Thu, Jul 18, 2013 at 12:52:37PM +0800, Xiao Guangrong wrote:
> >> Currently, fast page fault tries to fix mmio page fault when the
> >> generation number is invalid (spte.gen != kvm.gen) and returns to
> >> guest to retry the fault since it sees the last spte is nonpresent
> >> which causes infinity loop
> >>
> >> It can be triggered only on AMD host since the mmio page fault is
> >> recognized as ept-misconfig
> >>
> > We still call into regular page fault handler from ept-misconfig
> > handler, but fake zero error_code we provide makes page_fault_can_be_fast()
> > return false.
>
> Yes.
>
> >
> > Shouldn't shadow paging trigger this too? I haven't encountered this on
> > Intel without ept.
>
> Since currently fast page fault only works for direct mmu. :)
Ah, yes. So with shadow page and paging disabled in a guest is can
happen eventually, but we do not trigger it for some reason?
--
Gleb.
next prev parent reply other threads:[~2013-07-18 6:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 4:52 [PATCH] KVM: MMU: avoid fast page fault fixing mmio page fault Xiao Guangrong
2013-07-18 4:55 ` Xiao Guangrong
2013-07-18 5:31 ` Gleb Natapov
2013-07-18 6:01 ` Xiao Guangrong
2013-07-18 6:06 ` Gleb Natapov [this message]
2013-07-18 6:25 ` Xiao Guangrong
2013-07-18 6:28 ` Gleb Natapov
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=20130718060628.GA15613@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=xiaoguangrong@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).