From: Andi Kleen <andi@firstfloor.org>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Andi Kleen <andi@firstfloor.org>,
jolsa@redhat.com, linux-kernel@vger.kernel.org,
namhyung@kernel.org, acme@infradead.org
Subject: Re: perf: Add support for full Intel event lists v7
Date: Tue, 8 Jul 2014 21:28:33 +0200 [thread overview]
Message-ID: <20140708192833.GI18735@two.firstfloor.org> (raw)
In-Reply-To: <20140708184311.GA14707@us.ibm.com>
Thanks for testing.
On Tue, Jul 08, 2014 at 11:43:11AM -0700, Sukadev Bhattiprolu wrote:
> | The JSON format and perf parser has some minor Intelisms, but they
> | are simple and small and optional. It's easy to extend, so it would be
> | possible to use it for other CPUs too, add different pmu attributes, and
> | add new download sites to the downloader tool.
>
> Is there a minimal set of JSON entries an architecture would need ?
That should be enough, assuming the EventCode is enough to select
the event.
>
> I tried the following on Power
> [
> {
> "EventCode": "2",
> "EventName": "PM_INST_CMPL",
> "BriefDescription": "Instructions completed",
> "PublicDescription": "Number of PPC instructions finished",
> },
> {
> "EventCode": "0x1E",
> "EventName": "PM_CYC",
> "BriefDescription": "Cycles completed",
> "PublicDescription": "Number of PPC cycles finished",
> }
> ]
>
> /tmp/perf record --events-file=/tmp/power8.json -e PM_INST_CMPL sleep 1
>
> works, but for some TBD reason,
>
> /tmp/perf list --events-file=/tmp/power8.json doesn't list PM_INST_CMPL.
Works for me with your input file:
% perf list --events-file t.json
...
pm_cyc [Cycles completed]
pm_inst_cmpl [Instructions completed]
> Another observation was that the order of --events-file and -e is significant.
> Maybe worth a note in the man page.
Will add.
> Can you specify the qualifiers like ':k' or ':ku' with the events on
> Intel ?
>to only monitor kernel or user ? Or do they need some additional JSON
> entries ?
They can be all specified.
> With the above events file, I get "invalid event" for 'PM_INST_CMPL:u'
It works in new style syntax, like
perf stat --events-file t.json -e cpu/pm_inst_cmpl/u ls
Thanks,
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2014-07-08 19:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 23:15 Andi Kleen
2014-06-27 23:15 ` [PATCH 1/9] perf, tools: Add jsmn `jasmine' JSON parser v3 Andi Kleen
2014-06-27 23:15 ` [PATCH 2/9] perf, tools: Add support for text descriptions of events and alias add Andi Kleen
2014-07-09 22:19 ` Jiri Olsa
2014-07-11 22:55 ` Andi Kleen
2014-07-09 22:19 ` Jiri Olsa
2014-06-27 23:15 ` [PATCH 3/9] perf, tools: Add support for reading JSON event files v3 Andi Kleen
2014-07-09 22:19 ` Jiri Olsa
2014-07-09 22:19 ` Jiri Olsa
2014-07-09 22:19 ` Jiri Olsa
2014-07-10 0:05 ` Andi Kleen
2014-07-10 6:25 ` Jiri Olsa
2014-07-10 14:22 ` Andi Kleen
2014-07-09 22:20 ` Jiri Olsa
2014-07-10 0:06 ` Andi Kleen
2014-06-27 23:15 ` [PATCH 4/9] perf, tools: Automatically look for event file name for cpu v3 Andi Kleen
2014-07-09 22:19 ` Jiri Olsa
2014-06-27 23:16 ` [PATCH 5/9] perf, tools: Add perf download to download event files v4 Andi Kleen
2014-07-09 22:20 ` Jiri Olsa
2014-07-10 0:07 ` Andi Kleen
2014-06-27 23:16 ` [PATCH 6/9] perf, tools: Allow events with dot Andi Kleen
2014-07-09 22:18 ` Jiri Olsa
2014-06-27 23:16 ` [PATCH 7/9] perf, tools: Query terminal width and use in perf list Andi Kleen
2014-06-27 23:16 ` [PATCH 8/9] perf, tools, test: Add test case for alias and JSON parsing v2 Andi Kleen
2014-07-09 22:20 ` Jiri Olsa
2014-07-09 22:20 ` Jiri Olsa
2014-06-27 23:16 ` [PATCH 9/9] perf, tools: Add a --quiet flag to perf list Andi Kleen
2014-07-08 18:43 ` perf: Add support for full Intel event lists v7 Sukadev Bhattiprolu
2014-07-08 19:28 ` Andi Kleen [this message]
2014-07-08 21:49 ` Sukadev Bhattiprolu
2014-07-09 22:18 ` Jiri Olsa
2014-07-11 23:59 Andi Kleen
2014-07-18 8:57 ` 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=20140708192833.GI18735@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@infradead.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sukadev@linux.vnet.ibm.com \
/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