From: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>
To: xen-devel@lists.xen.org
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Lin Ming <mlin@ss.pku.edu.cn>,
wei.huang2@amd.com, marcus.granado@citrix.com, wei.wang2@amd.com,
Konrad Rzeszutek Wilk <konrad@darnok.org>
Subject: Re: Virtualization of the CPU Performance Monitoring Unit
Date: Tue, 17 Apr 2012 08:11:19 +0200 [thread overview]
Message-ID: <58047712.uBa5W5J32N@amur> (raw)
In-Reply-To: <20120416173936.GD18314@phenom.dumpdata.com>
Am Montag 16 April 2012, 13:39:36 schrieb Konrad Rzeszutek Wilk:
> On Mon, Apr 16, 2012 at 04:16:07PM +0800, Lin Ming wrote:
> > On Wed, Apr 11, 2012 at 10:30 PM, Lin Ming <mlin@ss.pku.edu.cn> wrote:
> >
> > [....]
> >
> > >> That isn't actually true. If you run it, you will see it working
> > >> in the guest - it just that it does not use the performence counters
> > >> but instead uses the timer to sample data.
> > >
> > > Right, I mean "hardware event" does not work.
> > >
> > > Hardware event, for example, perf top -e cycles, does not work.
> >
> > Just found that vpmu is disabled by default.
> > You need to pass xen boot parameter "vpmu" to make hardware event work.
>
> Oh, I wonder why it was disabled by default? Wei, would you know
> by any chance?
This had to do with a problem in the intel nehalem processors which could cause
endless interrupt loops in the hypervisor if a hvm guest uses the performance
counters so Keir proposed to add the vpmu boot flag.
http://lists.xen.org/archives/html/xen-devel/2009-10/msg01460.html
and
http://lists.xen.org/archives/html/xen-devel/2009-11/msg00088.html
Dietmar
>
> >
> > > Software event, for example, perf top -e cpu-clock, works.
> >
> > So both hardware and software event work in DomU.
> > Great!
>
> Excellent!
> >
> > >
> > >>
> > >> > Run "perf top", but no data was collected.
> > >>
> > >> Hm, I am able to collect data using Fedora Core 16 PV guest.
> > >> For dom0 or domU? For dom0 there is a bug somewhere where
> > >
> > > For domU HVM guest.
> > > I have problem to run domU PV guest. Still looking at it.
> > >
> > >> the machine crashes after 30 seconds or so - hadn't actually
> > >> gotten to the bottom of it. There was an email thread:
> > >> https://lkml.org/lkml/2012/2/12/74 about this.
> > >>
> > >> Patches are most welcome!
> >
> > Here are the patches.
> > https://lkml.org/lkml/2012/4/15/12
>
> Let me play with them a bit. At first glance they look ok - but I recall
> Peter Z saying something about not implementing the IRQ WORKER, but I can't
> recall the reasons.
> >
> > Regards,
> > Lin Ming
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
--
Company details: http://ts.fujitsu.com/imprint.html
prev parent reply other threads:[~2012-04-17 6:11 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
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 [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=58047712.uBa5W5J32N@amur \
--to=dietmar.hahn@ts.fujitsu.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@darnok.org \
--cc=marcus.granado@citrix.com \
--cc=mlin@ss.pku.edu.cn \
--cc=wei.huang2@amd.com \
--cc=wei.wang2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).