From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: MMU: Don't flush shadow when enabling dirty tracking
Date: Mon, 27 Dec 2010 11:16:42 +0200 [thread overview]
Message-ID: <4D18597A.1040602@redhat.com> (raw)
In-Reply-To: <20101227130651.7175e8b5.yoshikawa.takuya@oss.ntt.co.jp>
On 12/27/2010 06:06 AM, Takuya Yoshikawa wrote:
> Avi Kivity<avi@redhat.com> wrote:
>
> > Instead, drop large mappings, which were the reason we dropped shadow.
> >
> > Signed-off-by: Avi Kivity<avi@redhat.com>
> > ---
> > arch/x86/kvm/mmu.c | 10 ++++++----
> > virt/kvm/kvm_main.c | 7 +------
> > 2 files changed, 7 insertions(+), 10 deletions(-)
> >
> > diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> > index 43bd5e3..1bbe2c0 100644
> > --- a/arch/x86/kvm/mmu.c
> > +++ b/arch/x86/kvm/mmu.c
> > @@ -3444,14 +3444,16 @@ 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)
> > + for (i = 0; i< PT64_ENT_PER_PAGE; ++i) {
> > + if (sp->role.level != PT_PAGE_TABLE_LEVEL
> > + && is_large_pte(pt[i]))
> > + drop_spte(kvm,&pt[i],
> > + shadow_trap_nonpresent_pte);
> > /* avoid RMW */
> > if (is_writable_pte(pt[i]))
> > update_spte(&pt[i], pt[i]& ~PT_WRITABLE_MASK);
> > + }
> > }
> > kvm_flush_remote_tlbs(kvm);
> > }
>
> What is the difference from the similar part in rmap_write_protect()?
>
> === from rmap_write_protect() ===
>
> /* check for huge page mappings */
> for (i = PT_DIRECTORY_LEVEL;
> i< PT_PAGE_TABLE_LEVEL + KVM_NR_PAGE_SIZES; ++i) {
> rmapp = gfn_to_rmap(kvm, gfn, i);
> spte = rmap_next(kvm, rmapp, NULL);
> while (spte) {
> BUG_ON(!spte);
> BUG_ON(!(*spte& PT_PRESENT_MASK));
> BUG_ON((*spte& (PT_PAGE_SIZE_MASK|PT_PRESENT_MASK)) != (PT_PAGE_SIZE_MASK|PT_PRESENT_MASK));
> pgprintk("rmap_write_protect(large): spte %p %llx %lld\n", spte, *spte, gfn);
> if (is_writable_pte(*spte)) {
> drop_spte(kvm, spte,
> shadow_trap_nonpresent_pte);
> --kvm->stat.lpages;
> spte = NULL;
> write_protected = 1;
> }
> spte = rmap_next(kvm, rmapp, spte);
> }
> }
> ===
Shouldn't be any. I forgot to rmap_remove() and to update kvm_stat,
thanks for pointing it out.
I'll post an updated patch. We'll want to share code between the two
later on.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-12-27 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 11:23 [PATCH] KVM: MMU: Don't flush shadow when enabling dirty tracking Avi Kivity
2010-12-27 4:06 ` Takuya Yoshikawa
2010-12-27 9:16 ` Avi Kivity [this message]
2010-12-27 9:25 ` Avi Kivity
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=4D18597A.1040602@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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