[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABPqkBTeuD==RY9xORYyUhtZm0cXAFw7FEPocMsdCbcqTUS3bg@mail.gmail.com>
Date: Mon, 22 Oct 2012 17:44:08 +0200
From: Stephane Eranian <eranian@...gle.com>
To: Andi Kleen <ak@...ux.intel.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
"mingo@...e.hu" <mingo@...e.hu>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Jiri Olsa <jolsa@...hat.com>
Subject: Re: [PATCH v2 1/2] perf tools: add event modifier to request
exclusive PMU access
On Mon, Oct 22, 2012 at 5:39 PM, Andi Kleen <ak@...ux.intel.com> wrote:
>> 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.
>
Ok, I understand now.
But I am wondering what would be the meaning of:
$ perf stat -e instructions-p ...
I know the answer, because I know what's going on under the
hood. But what about the average user?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists