From: Anthony Liguori <anthony@codemonkey.ws>
To: Balaji Rao <balajirrao@gmail.com>
Cc: kvm-devel@lists.sourceforge.net, balbir@in.ibm.com
Subject: Re: [RFC] Performance monitoring units and KVM
Date: Sat, 16 Feb 2008 16:04:43 -0600 [thread overview]
Message-ID: <47B75DFB.1030901@codemonkey.ws> (raw)
In-Reply-To: <200802162304.43141.balajirrao@gmail.com>
Balaji Rao wrote:
> 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.
>
I think performance monitors are no different than anything else in
KVM. We should virtualize as much as possible and by default provide
only the common subset to the guest supported by the majority of hardware.
Then we can use mechanisms like QEMU's CPU support to enable additional
features that may be available and unique to the underlying hardware.
It's then up to the management tools to deal with migratability since
they've explicitly enabled the feature.
Regards,
Anthony Liguori
> The other option is to pass through the real PMU to the guest. I believe this
> approach is far better in the sense that,
>
> 1. All the available events in the host hardware can be passed on to the guest,
> which can be used by oprofile to profile the guest and trackdown slowdowns
> introduced due to virtualization.
>
> 2. Its much cleaner and easier to pass through the PMU.
>
> Yes, this approach breaks live migration. Migration should not be possible
> *only* when the PMU is being used by oprofile. We can mark the guest as
> unmigratable in such situations. Once the PMU is not being used, migration can
> be performed normally.
>
> Note, this requires a small change to oprofile source. Upon migration, oprofile
> should be made to re-identify the CPU and use the perf mon events appropriate
> to that CPU. I think this could be done by having a migrate_notifier, or
> something like that..
>
> Please provide comments on this.
>
>
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2008-02-16 22:04 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 [this message]
2008-02-17 4:43 ` Balaji Rao
2008-02-18 19:39 ` Markus Armbruster
2008-02-19 16:05 ` 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=47B75DFB.1030901@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox