From: Andi Kleen <ak@linux.intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, acme@redhat.com, jolsa@redhat.com
Subject: Re: [PATCH v2 1/2] perf tools: add event modifier to request exclusive PMU access
Date: Mon, 22 Oct 2012 06:53:58 -0700 [thread overview]
Message-ID: <20121022135358.GJ2095@tassilo.jf.intel.com> (raw)
In-Reply-To: <1350912052-10066-2-git-send-email-eranian@google.com>
On Mon, Oct 22, 2012 at 03:20:51PM +0200, Stephane Eranian wrote:
> This patch adds the x modifier for events. It allows users to
> request exclusive PMU access (attr->exclusive):
>
> perf stat -e cycles:x ......
> or
> perf stat -e cpu/cycles/x ....
>
> Exclusive mode is a feature of perf_events which was not yet
> supported by the perf tool. Some events may require exclusive
> PMU access (like on Intel SandyBridge).
You probably should add it also to be readable from sysfs
(like I did with precise in my haswell patchkit)
Then the SNB version of instructions-p can just force this
without the user having to do anything special.
-Andi
next prev parent reply other threads:[~2012-10-22 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 13:20 [PATCH v2 0/2] perf: enforce exclusive PMU access for SNB INST_RETIRED:PREC_DIST Stephane Eranian
2012-10-22 13:20 ` [PATCH v2 1/2] perf tools: add event modifier to request exclusive PMU access Stephane Eranian
2012-10-22 13:53 ` Andi Kleen [this message]
2012-10-22 14:55 ` Stephane Eranian
2012-10-22 15:39 ` Andi Kleen
2012-10-22 15:44 ` Stephane Eranian
2012-10-22 15:59 ` Peter Zijlstra
2012-10-22 16:08 ` Stephane Eranian
2012-10-22 17:08 ` Peter Zijlstra
2012-10-22 13:20 ` [PATCH v2 2/2] perf: enforce SNB exclusive access for INST_RETIRED:PREC_DIST Stephane Eranian
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=20121022135358.GJ2095@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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
Powered by JetHome