From: David Ahern <dsahern@gmail.com>
To: Brendan Gregg <brendan.d.gregg@gmail.com>
Cc: "linux-perf-use." <linux-perf-users@vger.kernel.org>
Subject: Re: perf CPU profiling in Xen guest fail & workaround
Date: Wed, 29 Jul 2015 14:02:23 -0600 [thread overview]
Message-ID: <55B9314F.70800@gmail.com> (raw)
In-Reply-To: <CAE40pdfEv5aFDUf_ixp_mtq9T1NQ4sCkhS211EwaaeCg7a=8NQ@mail.gmail.com>
On 7/29/15 1:27 PM, Brendan Gregg wrote:
> Thanks, yes. This took me by surprise: I've been profiling different
> Xen guests for over a year, but this is the first time I've hit this.
>
> All my other Xen guests:
>
> # dmesg | grep Performance
> [ 0.058664] Performance Events: unsupported p6 CPU model 62 no PMU
> driver, software events only.
>
> This linux 4.1 Xen guest:
>
> # dmesg | grep Performance
> [ 0.258140] Performance Events: 16-deep LBR, IvyBridge events,
> Intel PMU driver.
yep and since the hypervisor lies perf has no means of knowing to
fallback to cpu-clock.
next prev parent reply other threads:[~2015-07-29 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 19:04 perf CPU profiling in Xen guest fail & workaround Brendan Gregg
2015-07-29 19:15 ` David Ahern
2015-07-29 19:27 ` Brendan Gregg
2015-07-29 20:02 ` David Ahern [this message]
2015-07-29 22:21 ` Andi Kleen
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=55B9314F.70800@gmail.com \
--to=dsahern@gmail.com \
--cc=brendan.d.gregg@gmail.com \
--cc=linux-perf-users@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