Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: Exit timing - results online
Date: Mon, 10 Nov 2008 08:28:41 +0000	[thread overview]
Message-ID: <4917F0B9.3050006@linux.vnet.ibm.com> (raw)
In-Reply-To: <4912D42A.6030702@linux.vnet.ibm.com>

Hollis Blanchard wrote:
> On Thu, 2008-11-06 at 12:25 +0100, Christian Ehrhardt wrote:
>   
>> Hi,
>> I just added the following page to our wiki based online documentation 
>> to show some numbers on kvmppc as of today.
>> You can find that page at thew wiki entry:
>>   PowerPC_Exittimings 
>> <http://kvm.qumranet.com/kvmwiki/PowerPC_Exittimings> - an overview of 
>> workload dependent overhead on non hardware assisted powerpc virtualization
>>   (http://kvm.qumranet.com/kvmwiki/PowerPC_Exittimings)
>>     
>
> Very interesting; thanks for putting these numbers together Christian.
>
> I'm interested by the instruction emulation, which shows up as the
> highest cost in every workload. That suggests that even small
> improvements to the emulation path, such as using a better lookup than
> nested switch statements, could have a significant effect on throughput.
>
> It's also interesting that the average is really close to the minimum,
> but the standard deviation is huge. That suggests that the vast majority
> of exits take the minimum amount of time, but a few exits take a *ton*
> of time. Looking through the set of instructions we emulate on 440, it
> looks like the only even slightly sophisticated ones are rfi, tlbwe, and
> tlbsx...
>
>   
Yeah I extended my patch a bit to now account several different 
subcategories of the emulation.
One issue was that a idling guest setting MSR[WE] came via the emulation 
path and recorded all the time a kvm_block waited until there was work 
for the cpu.

I updated the numbers on the wiki page on Friday.

-- 

Grüsse / regards, 
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization


      parent reply	other threads:[~2008-11-10  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 11:25 Exit timing - results online Christian Ehrhardt
2008-11-06 17:37 ` Hollis Blanchard
2008-11-10  8:28 ` Christian Ehrhardt [this message]

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=4917F0B9.3050006@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=kvm-ppc@vger.kernel.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