From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: merge kvm_flush_remote_tlbs when modifing shadow pte
Date: Tue, 18 Dec 2007 01:19:53 +0200 [thread overview]
Message-ID: <47670419.8060302@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A028595A0-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Dong, Eddie wrote:
> host side TLB flush can be merged together if multiple
> spte need to be write-protected.
>
> Signed-off-by: Yaozu (Eddie) Dong <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>
> diff --git a/drivers/kvm/mmu.c b/drivers/kvm/mmu.c
> index 92ac0d1..749db46 100644
> --- a/drivers/kvm/mmu.c
> +++ b/drivers/kvm/mmu.c
> @@ -524,9 +524,9 @@ static void rmap_write_protect(struct kvm *kvm, u64
> gfn)
> rmap_printk("rmap_write_protect: spte %p %llx\n", spte,
> *spte);
> if (is_writeble_pte(*spte))
> set_shadow_pte(spte, *spte & ~PT_WRITABLE_MASK);
> - kvm_flush_remote_tlbs(kvm);
> spte = rmap_next(kvm, rmapp, spte);
> }
> + kvm_flush_remote_tlbs(kvm);
> }
>
I think this can be improved; in case we don't touch the shadow pte at
all, there is no need to flush the tlbs.
Also, please pull from kvm.git; things have moved around (mmu.c is now
in arch/x86/kvm/).
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
next prev parent reply other threads:[~2007-12-17 23:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 21:53 merge kvm_flush_remote_tlbs when modifing shadow pte Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A028595A0-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-17 23:19 ` Avi Kivity [this message]
[not found] ` <47670419.8060302-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-18 1:12 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A028596B5-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-18 15:26 ` 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=47670419.8060302@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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