From: Peter Zijlstra <peterz@infradead.org>
To: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>, David Ahern <dsahern@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: perf with precise attribute kills all KVM based VMs
Date: Mon, 09 Jul 2012 16:47:48 +0200 [thread overview]
Message-ID: <1341845268.3462.80.camel@twins> (raw)
In-Reply-To: <4FFAED16.7050204@redhat.com>
On Mon, 2012-07-09 at 17:39 +0300, Avi Kivity wrote:
> > Disabling PEBS events for guests isn't pretty though..
>
> We already have atomic MSR switching at guest entry/exit time. So it's
> not pretty in terms of not getting full profiling, but the code won't be
> too hard. Basically we just have to exclude_guest any pebs event.
OK, so ideally we'd do something like the below, except of course that
that isn't backwards compatible and will break the world :/
bugger that
---
--- a/arch/x86/kernel/cpu/perf_event.c
+++ b/arch/x86/kernel/cpu/perf_event.c
@@ -336,6 +338,9 @@ int x86_setup_perfctr(struct perf_event *event)
/* BTS is currently only allowed for user-mode. */
if (!attr->exclude_kernel)
return -EOPNOTSUPP;
+
+ if (!attr->exclude_guest)
+ return -EOPNOTSUPP;
}
hwc->config |= config;
@@ -378,6 +383,9 @@ int x86_pmu_hw_config(struct perf_event *event)
if (event->attr.precise_ip) {
int precise = 0;
+ if (!event->attr.exclude_guest)
+ return -EOPNOTSUPP;
+
/* Support for constant skid */
if (x86_pmu.pebs_active && !x86_pmu.pebs_broken) {
precise++;
next prev parent reply other threads:[~2012-07-09 14:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 14:12 perf with precise attribute kills all KVM based VMs David Ahern
2012-07-09 14:19 ` Gleb Natapov
2012-07-09 14:24 ` Peter Zijlstra
2012-07-09 14:36 ` Gleb Natapov
2012-07-09 14:39 ` Avi Kivity
2012-07-09 14:47 ` David Ahern
2012-07-09 14:49 ` Peter Zijlstra
2012-07-09 14:51 ` Avi Kivity
2012-07-09 14:54 ` Gleb Natapov
2012-07-09 14:57 ` Gleb Natapov
2012-07-09 14:59 ` Peter Zijlstra
2012-07-10 23:38 ` David Ahern
2012-07-11 7:10 ` Gleb Natapov
2012-07-11 9:49 ` Peter Zijlstra
2012-07-11 9:53 ` Gleb Natapov
2012-07-11 13:34 ` David Ahern
2012-07-12 4:11 ` David Ahern
2012-07-12 4:29 ` Gleb Natapov
2012-07-12 15:20 ` David Ahern
2012-07-12 16:06 ` Gleb Natapov
2012-07-12 16:13 ` Gleb Natapov
2012-07-12 16:58 ` Peter Zijlstra
2012-07-16 1:51 ` David Ahern
2012-07-15 8:07 ` Avi Kivity
2012-07-15 13:00 ` David Ahern
2012-07-15 13:03 ` Avi Kivity
2012-07-16 1:52 ` David Ahern
2012-07-16 2:19 ` David Ahern
2012-07-20 23:34 ` David Ahern
2012-07-22 9:52 ` Avi Kivity
2012-07-09 14:52 ` David Ahern
2012-07-09 14:58 ` David Ahern
2012-07-09 15:18 ` David Ahern
2012-07-09 14:47 ` Peter Zijlstra [this message]
2012-07-20 23:35 ` David Ahern
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=1341845268.3462.80.camel@twins \
--to=peterz@infradead.org \
--cc=avi@redhat.com \
--cc=dsahern@gmail.com \
--cc=gleb@redhat.com \
--cc=linux-kernel@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 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.