From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: KVM: MMU: only write protect mappings at pagetable level
Date: Wed, 22 Dec 2010 13:07:23 +0200 [thread overview]
Message-ID: <4D11DBEB.8050008@redhat.com> (raw)
In-Reply-To: <20101222110157.GA4266@amt.cnet>
On 12/22/2010 01:01 PM, Marcelo Tosatti wrote:
> If a pagetable contains a writeable large spte, all of its sptes will be
non-writeable
> write protected, including non-leaf ones, leading to endless pagefaults.
>
> Do not write protect pages above PT_PAGE_TABLE_LEVEL, as the spte fault
> paths assume non-leaf sptes are writable.
>
> Signed-off-by: Marcelo Tosatti<mtosatti@redhat.com>
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index c3853d5..c716ff8 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -3442,6 +3442,9 @@ void kvm_mmu_slot_remove_write_access(struct kvm *kvm, int slot)
> if (!test_bit(slot, sp->slot_bitmap))
> continue;
>
> + if (sp->role.level != PT_PAGE_TABLE_LEVEL)
> + continue;
> +
> pt = sp->spt;
> for (i = 0; i< PT64_ENT_PER_PAGE; ++i)
> /* avoid RMW */
But what about large leaf sptes? Don't we want to write protect, or
perhaps drop them?
I think write-protecting leaf sptes and ignoring nonleaf sptes should work.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-12-22 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 11:01 KVM: MMU: only write protect mappings at pagetable level Marcelo Tosatti
2010-12-22 11:07 ` Avi Kivity [this message]
2010-12-22 11:12 ` Marcelo Tosatti
2010-12-22 13:01 ` Avi Kivity
2010-12-22 13:06 ` Marcelo Tosatti
2010-12-22 14:06 ` Avi Kivity
2010-12-22 17:48 ` Alex Williamson
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=4D11DBEB.8050008@redhat.com \
--to=avi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox