public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	KVM list <kvm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] KVM MMU: allow shadow page become unsync at creating time
Date: Fri, 30 Apr 2010 12:54:00 +0300	[thread overview]
Message-ID: <4BDAA8B8.9030103@redhat.com> (raw)
In-Reply-To: <4BDA9CD0.6070501@cn.fujitsu.com>

On 04/30/2010 12:03 PM, Xiao Guangrong wrote:
> Allow new shadow page become unsync when is created, then we no need
> write-protect the 'sp->gfn', this idea is from Avi:
>
> |Another interesting case is to create new shadow pages in the unsync
> |state. That can help when the guest starts a short lived process: we
> |can avoid write protecting its pagetables completely
>
>    

Any idea how this improves performance?  A kernel build has a lot of 
short lived processes, might see an improvement there.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  parent reply	other threads:[~2010-04-30  9:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4BDA9C37.9070602@cn.fujitsu.com>
2010-04-30  9:52 ` [PATCH 1/4] KVM MMU: fix race in invlpg code Avi Kivity
     [not found] ` <4BDA9C86.8080204@cn.fujitsu.com>
     [not found]   ` <4BDA9CD0.6070501@cn.fujitsu.com>
2010-04-30  9:54     ` Avi Kivity [this message]
     [not found]     ` <4BDA9D58.6030407@cn.fujitsu.com>
2010-04-30  9:56       ` [PATCH 4/4] KVM MMU: do not intercept invlpg if 'oos_shadow' is disabled Avi Kivity
2010-05-05 12:54         ` Xiao Guangrong
2010-05-05 14: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=4BDAA8B8.9030103@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