From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: 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 14:49:23 -0700 [thread overview]
Message-ID: <20140708214923.GA18523@us.ibm.com> (raw)
In-Reply-To: <20140708192833.GI18735@two.firstfloor.org>
Andi Kleen [andi@firstfloor.org] wrote:
| Works for me with your input file:
|
| % perf list --events-file t.json
| ...
| pm_cyc [Cycles completed]
| pm_inst_cmpl [Instructions completed]
Ah, lower case.
|
| > 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
Yes, thanks.
Sukadev
next prev parent reply other threads:[~2014-07-08 21:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 23:15 perf: Add support for full Intel event lists v7 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
2014-07-08 21:49 ` Sukadev Bhattiprolu [this message]
2014-07-09 22:18 ` Jiri Olsa
-- strict thread matches above, loose matches on Subject: below --
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=20140708214923.GA18523@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.