mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH v2 1/2] perf tools: add event modifier to request exclusive PMU access
Date: Mon, 22 Oct 2012 08:39:52 -0700	[thread overview]
Message-ID: <20121022153952.GM2095@tassilo.jf.intel.com> (raw)
In-Reply-To: <CABPqkBTJsZHdvp+Tm3SGJCfJ7eMFaqQR8pd9eoh5KyBo3k6o3Q@mail.gmail.com>

> But maybe you're talking about a generic event exports in
> /sys/device/cpu/events.
> But why would I expose prec_dist there. And under what name?

I already exposed it in the Haswell patchkit (instructions-p)

I also exposed precise there so that some events can be forced PEBS

If you want to expose it on Sandy Bridge too you need to add the 
event to the user tool grammar, like I did for precise.

Then user can just use

perf record -e instructions-p ...

and the kernel does automagically the right thing.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

  reply	other threads:[~2012-10-22 15:40 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
2012-10-22 14:55     ` Stephane Eranian
2012-10-22 15:39       ` Andi Kleen [this message]
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=20121022153952.GM2095@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
all inboxes | Powered by JetHome®