public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Christian Ehrhardt
	<ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Subject: Re: [PATCH 0 of 6] PowerPC KVM patches for 2.6.29
Date: Wed, 03 Dec 2008 10:04:29 -0600	[thread overview]
Message-ID: <1228320269.10084.7.camel@localhost.localdomain> (raw)
In-Reply-To: <49366E68.4080904-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Wed, 2008-12-03 at 13:32 +0200, Avi Kivity wrote:
> Hollis Blanchard wrote:
> > Hi Avi, here's the latest batch of PowerPC kernel patches.
> >
> > The first set dramatically improve performance. Most importantly, we add
> > support for large host pages with KVM (i.e. PAGE_SHIFT > 12). (Large *guest*
> > pages have already been supported since day 1, since the guest kernel uses
> > them for the linear map.) Followup patches further improve performance by
> > changing how we manage the shadow TLB.
> >
> > The last two add some accounting code to easily discover performance
> > bottlenecks. This is especially important since the 440 core lacks performance
> > monitoring hardware.
> >
> > These patches, in conjunction with 64KB pages on guest and host, get us to 96%
> > of native performance for compute-bound workloads, which I'm pretty happy
> > with. See http://kvm.qumranet.com/kvmwiki/PowerPC_Exittimings for more
> > details (those statistics were gathered using the accounting patches).
> >
> > These have been tested pretty thoroughly for several weeks. Please apply for
> > 2.6.29. Thanks!
> >   
> 
> Applied all, thanks.

Thanks.

> I'm not thrilled about the private exit timing statistics gathering, 
> hopefully it can be morphed into the more general framework.

Is there anything in particular you have in mind? I think it could be
generally useful, but since x86 has hardware support for performance
monitoring, oprofile will already give you more accurate information. Of
course, I don't think you could extract standard deviation from an
oprofile report, and that has been very useful for us because it can
tell us e.g. 99% of instruction emulation is handled in the minimum
amount of time, but 1% takes hundreds of ms.

I'll let Christian comment when he gets back from vacation on Monday.

-- 
Hollis Blanchard
IBM Linux Technology Center

--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-12-03 16:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 21:51 [PATCH 0 of 6] PowerPC KVM patches for 2.6.29 Hollis Blanchard
2008-12-02 21:51 ` [PATCH 1 of 6] kvm: ppc: support large host pages Hollis Blanchard
2008-12-02 21:51 ` [PATCH 2 of 6] powerpc/44x: declare tlb_44x_index for use in C code Hollis Blanchard
2008-12-02 21:51 ` [PATCH 3 of 6] kvm: ppc: directly insert shadow mappings into the hardware TLB Hollis Blanchard
2008-12-02 21:51 ` [PATCH 4 of 6] kvm: ppc: save and restore guest mappings on context switch Hollis Blanchard
2008-12-02 21:51 ` [PATCH 5 of 6] kvm: ppc: Implement in-kernel exit timing statistics Hollis Blanchard
2008-12-02 21:51 ` [PATCH 6 of 6] kvm: ppc: mostly cosmetic updates to the exit timing accounting code Hollis Blanchard
2008-12-03 11:32 ` [PATCH 0 of 6] PowerPC KVM patches for 2.6.29 Avi Kivity
     [not found]   ` <49366E68.4080904-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-12-03 16:04     ` Hollis Blanchard [this message]
     [not found]       ` <1228320269.10084.7.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-12-03 17:06         ` Avi Kivity
2008-12-03 19:22           ` Hollis Blanchard
2008-12-03 19:31             ` Hollis Blanchard

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=1228320269.10084.7.camel@localhost.localdomain \
    --to=hollisb-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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