From: Peter Zijlstra <peterz@infradead.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Feng Tang <feng.tang@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf, x86: Enabled PEBS event to be exported in a raw format
Date: Tue, 03 Jul 2012 11:15:05 +0200 [thread overview]
Message-ID: <1341306905.23484.53.camel@twins> (raw)
In-Reply-To: <1341300987.11663.15.camel@concordia>
On Tue, 2012-07-03 at 17:36 +1000, Michael Ellerman wrote:
> On Fri, 2012-06-29 at 00:00 +0800, Feng Tang wrote:
> > From: Andi Kleen <ak@linux.intel.com>
> >
> > Add support for reporting PEBS records in a raw format that can
> > be then parsed by perf script.
> >
> > This is roughly similar to the existing AMD IBS support.
> >
> > This is mainly for advanced users and to experiment with
> > new usages. Widespread PEBS usages are expected to get higher
> > level interfaces over time, like the existing "precise ip" support.
>
> Hi folks,
>
> Pardon if I slightly hijack this thread, but we'd like to do something
> similar to this on powerpc.
Do expand. What does exact information does it provide?
> I've been telling people not to use PERF_SAMPLE_RAW because it provides
> no way for the consumer to know what data they're getting, and it's not
> extensible in any way.
>
> So is shovelling things out using PERF_SAMPLE_RAW generally acceptable
> for "advanced usage" scenarios?
No.
next prev parent reply other threads:[~2012-07-03 9:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 16:00 [PATCH] perf, x86: Enabled PEBS event to be exported in a raw format Feng Tang
2012-06-28 16:12 ` Peter Zijlstra
2012-06-28 16:15 ` Stephane Eranian
2012-06-28 16:19 ` Peter Zijlstra
2012-06-28 16:27 ` Stephane Eranian
2012-06-28 16:29 ` Peter Zijlstra
2012-06-28 18:26 ` Andi Kleen
2012-06-28 18:20 ` Andi Kleen
2012-06-28 20:51 ` Peter Zijlstra
2012-06-29 1:32 ` Feng Tang
2012-06-29 3:35 ` Andi Kleen
2012-06-29 12:49 ` Ingo Molnar
2012-07-03 7:36 ` Michael Ellerman
2012-07-03 9:15 ` Peter Zijlstra [this message]
2012-07-04 8:07 ` Michael Ellerman
2012-07-04 9:13 ` Peter Zijlstra
2012-07-05 15:57 ` Stephane Eranian
2012-07-07 7:27 ` Michael Ellerman
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=1341306905.23484.53.camel@twins \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=mingo@elte.hu \
--cc=x86@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