From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, Jiri Olsa <jolsa@redhat.com>,
Lin Ming <ming.m.lin@intel.com>, rostedt <rostedt@goodmis.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf, p4: Add format attributes
Date: Tue, 27 Mar 2012 19:12:50 +0400 [thread overview]
Message-ID: <20120327151250.GG11875@moon> (raw)
In-Reply-To: <1332860759.16159.233.camel@twins>
On Tue, Mar 27, 2012 at 05:05:59PM +0200, Peter Zijlstra wrote:
> >
> > Thanks a lot, Peter! This format description is somewhat
> > new to me (I think I've missed when it was introduced first
> > time).
>
> Yeah, its all brand-spanking new stuff.. see
> https://lkml.org/lkml/2012/1/16/146 , Jiri added a full fledged
> bison/yacc parser to perf so we can now write events like:
>
> perf stat -e cpu/event=0xb7,umask=0x01,offcore_rsp=0x500b/
>
> and it uses /sys/bus/event_source/devices/cpu/format/* to figure out how
> to convert that into perf_event_attr::config{,1,2} values.
>
> So with this patch you could, on your P4, write:
>
> perf stat -e cpu/cccr=0x1234,escr=0x4321,ht/
>
> and it would construct the perf_event_attr::config value 0x92344321 for
> you.
>
Ah, I see thanks for the reference, Peter!
> I've still not actually read the P4-PMU specs, so I don't know if
> there's anything more convenient we can do on P4. If there's a
> better/more useful format representation possible, don't hesitate to
> send a patch! :-)
Sure, I'll try to find some time tonight to read this brand
new stuff. And if I find something -- will send out. At moment
your patch should be more than enough ;)
Cyrill
next prev parent reply other threads:[~2012-03-27 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 14:50 [PATCH] perf, p4: Add format attributes Peter Zijlstra
2012-03-27 14:57 ` Cyrill Gorcunov
2012-03-27 15:05 ` Cyrill Gorcunov
2012-03-27 15:05 ` Peter Zijlstra
2012-03-27 15:07 ` Peter Zijlstra
2012-03-27 15:12 ` Cyrill Gorcunov [this message]
2012-03-27 22:03 ` Cyrill Gorcunov
2012-03-27 22:05 ` Peter Zijlstra
2012-03-27 22:11 ` Cyrill Gorcunov
2012-04-03 8:11 ` [tip:perf/urgent] perf/x86/p4: " tip-bot for Peter Zijlstra
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=20120327151250.GG11875@moon \
--to=gorcunov@openvz.org \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).