From: Avi Kivity <avi@redhat.com>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/6] KVM: MMU: support pte prefetch when intercepted guest #PF
Date: Tue, 15 Jun 2010 14:45:08 +0300 [thread overview]
Message-ID: <4C1767C4.7020506@redhat.com> (raw)
In-Reply-To: <4C16E974.8000304@cn.fujitsu.com>
On 06/15/2010 05:46 AM, Xiao Guangrong wrote:
> Hi Avi, Marcelo,
>
> This patchset support pte prefetch when intercepted guest #PF,
> the aim is to reduce guest #PF which can be intercepted by VMM.
>
> If we meet any failure in the prefetch path, we will exit it
> and not try other ptes to avoid become heavy path.
>
> During my performance test, under EPT enabled case, unixbench
> shows the performance improved ~1.2%,
Once the guest has faulted in all memory, we shouldn't see much
improvement, yes?
> user EPT disable case,
> unixbench shows the performance improved ~3.6%
>
I'm a little worried about this. In some workloads, prefetch can often
fail due to gpte.a=0 so we spend effort doing nothing. There is also
the issue of marking pages as accessed or even dirty when in fact the
guest did not access them.
We should map those pages with pte.a=pte.d=0 so we don't confuse host
memory management. On EPT (which lacks a/d bits) we can't enable it
(but we can on NPT).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-15 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 2:46 [PATCH 0/6] KVM: MMU: support pte prefetch when intercepted guest #PF Xiao Guangrong
2010-06-15 11:45 ` Avi Kivity [this message]
2010-06-17 7:49 ` Xiao Guangrong
2010-06-17 8:00 ` 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=4C1767C4.7020506@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