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 08:31:54 +0300 [thread overview]
Message-ID: <20130718053154.GY11772@redhat.com> (raw)
In-Reply-To: <1374123157-11142-1-git-send-email-xiaoguangrong@linux.vnet.ibm.com>
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.
Shouldn't shadow paging trigger this too? I haven't encountered this on
Intel without ept.
> Fix it by filtering the mmio page fault out in page_fault_can_be_fast
>
> Reported-by: Markus Trippelsdorf <markus@trippelsdorf.de>
> Tested-by: Markus Trippelsdorf <markus@trippelsdorf.de>
> Signed-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
> ---
> arch/x86/kvm/mmu.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index bf7af1e..3a9493a 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -2811,6 +2811,13 @@ exit:
> static bool page_fault_can_be_fast(struct kvm_vcpu *vcpu, u32 error_code)
> {
> /*
> + * Do not fix the mmio spte with invalid generation number which
> + * need to be updated by slow page fault path.
> + */
> + if (unlikely(error_code & PFERR_RSVD_MASK))
> + return false;
> +
> + /*
> * #PF can be fast only if the shadow page table is present and it
> * is caused by write-protect, that means we just need change the
> * W bit of the spte which can be done out of mmu-lock.
> --
> 1.8.1.4
--
Gleb.
next prev parent reply other threads:[~2013-07-18 5:32 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 [this message]
2013-07-18 6:01 ` Xiao Guangrong
2013-07-18 6:06 ` Gleb Natapov
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=20130718053154.GY11772@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 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.