From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH v2 1/7] KVM: MMU: optimize pte write path if don't have protected sp
Date: Wed, 18 May 2011 16:20:03 +0300 [thread overview]
Message-ID: <4DD3C783.8090003@redhat.com> (raw)
In-Reply-To: <20110518131247.GA10833@amt.cnet>
On 05/18/2011 04:12 PM, Marcelo Tosatti wrote:
> On Mon, May 16, 2011 at 02:25:02PM +0300, Avi Kivity wrote:
> > On 05/15/2011 06:20 PM, Xiao Guangrong wrote:
> > >Simply return from kvm_mmu_pte_write path if no shadow page is
> > >write-protected, then we can avoid to walk all shadow pages and hold
> > >mmu-lock
> >
> > Patchset looks like a very good cleanup (plus the nice optimization
> > in patch 1).
>
> What case is patch 1 optimizing for?
>
Say, kvmclock updates.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-05-18 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 15:20 [PATCH v2 1/7] KVM: MMU: optimize pte write path if don't have protected sp Xiao Guangrong
2011-05-15 15:22 ` [PATCH v2 2/7] KVM: use __copy_to_user/__clear_user to write guest page Xiao Guangrong
2011-05-15 15:25 ` [PATCH v2 3/7] KVM: fix uninitialized warning Xiao Guangrong
2011-05-15 15:26 ` [PATCH v2 4/7] KVM: MMU: abstract the operation of rmap Xiao Guangrong
2011-05-15 15:27 ` [PATCH v2 5/7] KVM: MMU: remove the arithmetic of parent pte rmap Xiao Guangrong
2011-05-15 15:27 ` [PATCH v2 6/7] KVM: MMU: cleanup for kvm_mmu_page_unlink_children Xiao Guangrong
2011-05-15 15:28 ` [PATCH v2 7/7] KVM: MMU: cleanup for dropping parent pte Xiao Guangrong
2011-05-16 11:25 ` [PATCH v2 1/7] KVM: MMU: optimize pte write path if don't have protected sp Avi Kivity
2011-05-18 13:12 ` Marcelo Tosatti
2011-05-18 13:20 ` Avi Kivity [this message]
2011-05-20 15:49 ` 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=4DD3C783.8090003@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong@cn.fujitsu.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