Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
	kvm-ppc@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
	Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH 00/13] KVM: MMU: fast page fault
Date: Tue, 17 Apr 2012 14:54:50 +0000	[thread overview]
Message-ID: <20120417235450.c0972c06034002d7173eeb40@gmail.com> (raw)
In-Reply-To: <4F8D6503.4040800@redhat.com>

On Tue, 17 Apr 2012 15:41:39 +0300
Avi Kivity <avi@redhat.com> wrote:

> > Since there are many known algorithms to predict hot memory pages,
> > the userspace will be able to tune the frequency of GET_DIRTY_LOG for such
> > parts not to get too many faults repeatedly, if we can restrict the range
> > of pages to protect.
> >
> > This is the fine-grained control.
> 
> Do you want per-page control, or just range-based?

Difficult question.

For live migration, range-based control may be enough duo to the locality
of WWS.

Thanks,
	Takuya

  reply	other threads:[~2012-04-17 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F742951.7080003@linux.vnet.ibm.com>
     [not found] ` <4F82E04E.6000900@redhat.com>
     [not found]   ` <20120409175829.GB21894@amt.cnet>
     [not found]     ` <4F8329D3.7000605@gmail.com>
     [not found]       ` <20120409194614.GB23053@amt.cnet>
     [not found]         ` <4F840DD2.3090101@redhat.com>
     [not found]           ` <20120410204031.ffb5b976225ac9fe6dae474e@gmail.com>
     [not found]             ` <4F842074.1050108@linux.vnet.ibm.com>
     [not found]               ` <20120411211514.35db29c11460516e604059b6@gmail.com>
     [not found]                 ` <4F857B61.9080602@linux.vnet.ibm.com>
     [not found]                   ` <20120411231441.9d0984672dd252b806f99128@gmail.com>
     [not found]                     ` <20120413232528.c5ddbddb3cc0870d6e85a332@gmail.com>
     [not found]                       ` <4F8A95CB.9070104@redhat.com>
2012-04-16 15:49                         ` [PATCH 00/13] KVM: MMU: fast page fault Takuya Yoshikawa
2012-04-16 16:02                           ` Avi Kivity
2012-04-17  6:26                           ` Xiao Guangrong
2012-04-17  7:51                             ` Avi Kivity
2012-04-17 12:37                               ` Takuya Yoshikawa
2012-04-17 12:41                                 ` Avi Kivity
2012-04-17 14:54                                   ` Takuya Yoshikawa [this message]
2012-04-17 14:56                                     ` Avi Kivity
2012-04-18 13:42                                       ` Takuya Yoshikawa

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=20120417235450.c0972c06034002d7173eeb40@gmail.com \
    --to=takuya.yoshikawa@gmail.com \
    --cc=avi@redhat.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=xiaoguangrong.eric@gmail.com \
    --cc=xiaoguangrong@linux.vnet.ibm.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