From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <takuya.yoshikawa@gmail.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 12:41:39 +0000 [thread overview]
Message-ID: <4F8D6503.4040800@redhat.com> (raw)
In-Reply-To: <20120417213748.f3c4ae8d0056676fd33a47c5@gmail.com>
On 04/17/2012 03:37 PM, Takuya Yoshikawa wrote:
> On Tue, 17 Apr 2012 10:51:40 +0300
> Avi Kivity <avi@redhat.com> wrote:
>
> > That's true with the write protect everything approach we use now. But
> > it's not true with range-based write protection, where you issue
> > GET_DIRTY_LOG on a range of pages and only need to re-write-protect them.
> >
> > (the motivation for that is to decrease the time between GET_DIRTY_LOG
> > and sending the page; as the time increases, the chances that the page
> > got re-dirtied go up).
>
> Thank you for explaining this.
>
> I was planning to give the userspace more freedom.
>
> 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?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-04-17 12:41 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 [this message]
2012-04-17 14:54 ` Takuya Yoshikawa
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=4F8D6503.4040800@redhat.com \
--to=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=takuya.yoshikawa@gmail.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