All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Marcus Granado <marcus.granado@citrix.com>
Cc: mike McClurg <mike.mcclurg@citrix.com>,
	"wei.huang2@amd.com" <wei.huang2@amd.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Lin Ming <mlin@ss.pku.edu.cn>
Subject: Re: Virtualization of the CPU Performance Monitoring Unit
Date: Wed, 11 Apr 2012 10:00:31 -0400	[thread overview]
Message-ID: <20120411140031.GD21703@andromeda.dapyr.net> (raw)
In-Reply-To: <4F84478A.5010701@citrix.com>

On Tue, Apr 10, 2012 at 03:45:30PM +0100, Marcus Granado wrote:
> On 08/04/12 07:48, Lin Ming wrote:
> >>2. The PMU project description in the wiki is vague. I know HVM guests
> >>support virtualized PMU. Please check vpmu.c files in /hvm, /svm, and /vmx
> >>directories. You better ask mentors for details (maybe this is XCP
> >>specific?).
> Yes, the description is vague, we should update the page. The idea was 
> to enable users to run hardware profilers in dom0 and in any domU, PV or 
> HVM. This would include implementing what is missing for dom0/PV 
> domains, and to confirm in HVM domains that profilers such as oprofile, 
> hwpmc, intel performance counter monitor at least are running without 
> problems in the existing vPMU implementation. The original idea was to 
> add support to XCP, but please feel free to add support to xen-unstable 
> and the latest linux kernel; XCP will use those at some point.

Hey Marcos,

I think we (you, Lin and me) should talk - if Lin is very interested in this,
it might make sense to focus first on the existing supported 'perf' framework
that Linux has - instead of the oprofile variant.

Lin, Marcos, what day/time would work for an IRC meeting on
irc.freenode.net?

> cheers,
> Marcus
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2012-04-11 14:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 15:41 Virtualization of the CPU Performance Monitoring Unit Lin Ming
2012-04-06 16:43 ` Wei Huang
2012-04-06 18:36   ` Konrad Rzeszutek Wilk
2012-04-08  6:58     ` Lin Ming
2012-04-10  9:52       ` Ian Campbell
2012-04-10 16:25         ` Lin Ming
2012-04-08  6:48   ` Lin Ming
2012-04-10 14:45     ` Marcus Granado
2012-04-10 16:26       ` Lin Ming
2012-04-11 14:00       ` Konrad Rzeszutek Wilk [this message]
2012-04-11 14:34         ` Lin Ming
2012-04-11 13:46     ` Konrad Rzeszutek Wilk
2012-04-11 14:30       ` Lin Ming
2012-04-16  8:16         ` Lin Ming
2012-04-16 17:39           ` Konrad Rzeszutek Wilk
2012-04-17  6:11             ` Dietmar Hahn

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=20120411140031.GD21703@andromeda.dapyr.net \
    --to=konrad@darnok.org \
    --cc=konrad.wilk@oracle.com \
    --cc=marcus.granado@citrix.com \
    --cc=mike.mcclurg@citrix.com \
    --cc=mlin@ss.pku.edu.cn \
    --cc=wei.huang2@amd.com \
    --cc=xen-devel@lists.xen.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 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.