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 v2] KVM: MMU: Don't flush shadow when enabling dirty tracking
Date: Mon, 27 Dec 2010 12:43:59 +0200 [thread overview]
Message-ID: <4D186DEF.2020900@redhat.com> (raw)
In-Reply-To: <20101227193547.c5691b89.yoshikawa.takuya@oss.ntt.co.jp>
On 12/27/2010 12:35 PM, Takuya Yoshikawa wrote:
> On Mon, 27 Dec 2010 12:08:45 +0200
> 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>
> > ---
> >
> > v2: maintain largepage stats
> >
> > arch/x86/kvm/mmu.c | 12 ++++++++----
> > virt/kvm/kvm_main.c | 7 +------
> > 2 files changed, 9 insertions(+), 10 deletions(-)
> >
> > diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> > index 43bd5e3..dc36088 100644
> > --- a/arch/x86/kvm/mmu.c
> > +++ b/arch/x86/kvm/mmu.c
> > @@ -3444,14 +3444,18 @@ 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);
> > + --kvm->stat.lpages;
> > + }
> > /* avoid RMW */
> > if (is_writable_pte(pt[i]))
> > update_spte(&pt[i], pt[i]& ~PT_WRITABLE_MASK);
>
> I'm a bit confused here.
> rmap_write_protect() does drop_spte() but update_spte() in
> /* check for huge page mappings */ loop.
>
rmap_write_protect() protects a 4k page, so it uses update_spte() to
drop the W bit, and drops large mappings that point to the same 4k
page. We can't drop the W bit from the large page, because that will
write protect 511 unrelated pages.
> I may be able to learn something from your share code later on.
>
Unlikely - I was thinking of sharing the
> + drop_spte(kvm,&pt[i],
> + shadow_trap_nonpresent_pte);
> + --kvm->stat.lpages;
bits. Now I'm thinking of dropping kvm->stat, I think we have all the
information it provides covered by tracepoints.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-12-27 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 10:08 [PATCH v2] KVM: MMU: Don't flush shadow when enabling dirty tracking Avi Kivity
2010-12-27 10:35 ` Takuya Yoshikawa
2010-12-27 10:43 ` Avi Kivity [this message]
2010-12-27 10:54 ` Takuya Yoshikawa
2011-01-04 14:28 ` 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=4D186DEF.2020900@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