All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kvm-devel@lists.sourceforge.net, balbir@in.ibm.com,
	Balaji Rao <balajirrao@gmail.com>
Subject: Re: [RFC] Performance monitoring units and KVM
Date: Tue, 19 Feb 2008 18:05:51 +0200	[thread overview]
Message-ID: <47BAFE5F.9060409@qumranet.com> (raw)
In-Reply-To: <87ejbaxdes.fsf@pike.pond.sub.org>

Markus Armbruster wrote:
> Balaji Rao <balajirrao@gmail.com> writes:
>
>   
>> Hi all!
>>
>> Earlier it was suggested that we go ahead with emulating Perf Mon Events in 
>> exposing it to the guest. The serious limitation in this approach is that we 
>> end up exposing only a small number of events to the guest, even though the 
>> host hardware is capable of much more. The only benefit this approach offers is 
>> that, it doesn't break live migration.
>>
>> The other option is to pass through the real PMU to the guest. I believe this 
>> approach is far better in the sense that,
>>     
>
> Do we really have an either/or alternative here?
>
>   

I think that PMU pass through makes more sense, due to the nature of 
existing non-paravirtualized tools.

> There are ways to use the PMU in guests that don't require costly
> virtualization of the real PMU.  They put the guest's performance
> monitoring interface at a level higher than hardware PMU.
>   

On the other hand, they will work only on very new guests.  Paravirt pmu 
makes sense, but it cannot replace the hardware pmu interface.


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      reply	other threads:[~2008-02-19 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16 17:34 [RFC] Performance monitoring units and KVM Balaji Rao
2008-02-16 22:04 ` Anthony Liguori
2008-02-17  4:43   ` Balaji Rao
2008-02-18 19:39 ` Markus Armbruster
2008-02-19 16:05   ` Avi Kivity [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=47BAFE5F.9060409@qumranet.com \
    --to=avi@qumranet.com \
    --cc=armbru@redhat.com \
    --cc=balajirrao@gmail.com \
    --cc=balbir@in.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.