From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: mingo@redhat.com, ak@linux.intel.com,
Michael Ellerman <mpe@ellerman.id.au>,
Jiri Olsa <jolsa@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: peterz@infradead.org, namhyung@kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v9 00/11] Add support for JSON event files.
Date: Mon, 13 Apr 2015 23:40:53 -0700 [thread overview]
Message-ID: <1428993665-2133-1-git-send-email-sukadev@linux.vnet.ibm.com> (raw)
This is another attempt to resurrect Andi Kleen's patchset so users
can specify perf events by their event names rather than raw codes.
This is a rebase of Andi Kleen's patchset from Jul 30, 2014[1] to 4.0.
(I fixed minor and not so minor conflicts).
This patchset includes the perf-download tool that was dropped and sets
the default download location to the (tools/perf/pmu-events/arch/...
directory in Linus's tree.
A follow-on patchset will include the actual JSON files for Powerpc, which
are currently available on github[2].
[1] https://lkml.org/lkml/2014/7/30/693
[2] https://github.com/open-power/power-pmu-events
Andi Kleen (9):
perf, tools: Add jsmn `jasmine' JSON parser
perf, tools: Add support for text descriptions of events and alias
add
perf, tools, list: Update perf list to output descriptions
perf, tools: Add support for reading JSON event files
perf, tools: Automatically look for event file name for cpu
perf, tools: Query terminal width and use in perf list
perf, tools: Add a new pmu interface to iterate over all events
perf, tools, test: Add test case for alias and JSON parsing
perf, tools: Add a --no-desc flag to perf list
Sukadev Bhattiprolu (2):
powerpc/perf: Implement get_cpu_str()
perf-download: Download the events json file
tools/perf/Documentation/perf-download.txt | 31 +++
tools/perf/Documentation/perf-list.txt | 29 ++-
tools/perf/Documentation/perf-record.txt | 9 +-
tools/perf/Documentation/perf-stat.txt | 8 +-
tools/perf/Makefile.perf | 12 +-
tools/perf/arch/powerpc/util/header.c | 12 ++
tools/perf/arch/x86/util/header.c | 19 +-
tools/perf/builtin-list.c | 18 +-
tools/perf/builtin-record.c | 3 +
tools/perf/builtin-stat.c | 2 +
tools/perf/perf-download.sh | 171 +++++++++++++++
tools/perf/tests/aliases.c | 59 ++++++
tools/perf/tests/builtin-test.c | 4 +
tools/perf/tests/tests.h | 1 +
tools/perf/util/cache.h | 1 +
tools/perf/util/jevents.c | 287 +++++++++++++++++++++++++
tools/perf/util/jevents.h | 9 +
tools/perf/util/jsmn.c | 313 ++++++++++++++++++++++++++++
tools/perf/util/jsmn.h | 67 ++++++
tools/perf/util/json.c | 162 ++++++++++++++
tools/perf/util/json.h | 13 ++
tools/perf/util/pager.c | 15 ++
tools/perf/util/parse-events.c | 4 +-
tools/perf/util/parse-events.h | 2 +-
tools/perf/util/pmu.c | 160 +++++++++++---
tools/perf/util/pmu.h | 5 +-
26 files changed, 1365 insertions(+), 51 deletions(-)
create mode 100644 tools/perf/Documentation/perf-download.txt
create mode 100755 tools/perf/perf-download.sh
create mode 100644 tools/perf/tests/aliases.c
create mode 100644 tools/perf/util/jevents.c
create mode 100644 tools/perf/util/jevents.h
create mode 100644 tools/perf/util/jsmn.c
create mode 100644 tools/perf/util/jsmn.h
create mode 100644 tools/perf/util/json.c
create mode 100644 tools/perf/util/json.h
--
1.7.9.5
next reply other threads:[~2015-04-14 6:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 6:40 Sukadev Bhattiprolu [this message]
2015-04-14 6:40 ` [PATCH v9 01/11] perf, tools: Add jsmn `jasmine' JSON parser Sukadev Bhattiprolu
2015-04-14 6:40 ` [PATCH v9 02/11] perf, tools: Add support for text descriptions of events and alias add Sukadev Bhattiprolu
2015-04-14 6:40 ` [PATCH v9 03/11] perf, tools, list: Update perf list to output descriptions Sukadev Bhattiprolu
2015-04-14 6:40 ` [PATCH v9 04/11] perf, tools: Add support for reading JSON event files Sukadev Bhattiprolu
2015-04-14 6:40 ` [PATCH v9 05/11] perf, tools: Automatically look for event file name for cpu Sukadev Bhattiprolu
2015-04-14 6:40 ` [PATCH v9 06/11] powerpc/perf: Implement get_cpu_str() Sukadev Bhattiprolu
2015-04-14 6:41 ` [PATCH v9 07/11] perf, tools: Query terminal width and use in perf list Sukadev Bhattiprolu
2015-04-14 6:41 ` [PATCH v9 08/11] perf, tools: Add a new pmu interface to iterate over all events Sukadev Bhattiprolu
2015-04-14 6:41 ` [PATCH v9 09/11] perf, tools, test: Add test case for alias and JSON parsing Sukadev Bhattiprolu
2015-04-14 6:41 ` [PATCH v9 10/11] perf, tools: Add a --no-desc flag to perf list Sukadev Bhattiprolu
2015-04-14 6:41 ` [PATCH v9 11/11] perf-download: Download the events json file Sukadev Bhattiprolu
2015-04-14 8:55 ` 'perf upgrade' (was: Re: [PATCH v9 00/11] Add support for JSON event files.) Ingo Molnar
2015-04-14 11:21 ` Michael Ellerman
2015-04-14 12:58 ` Ingo Molnar
2015-04-14 18:03 ` Sukadev Bhattiprolu
2015-04-14 22:53 ` Michael Ellerman
2015-04-15 9:25 ` Ingo Molnar
2015-04-15 19:17 ` Andi Kleen
2015-04-15 20:50 ` Sukadev Bhattiprolu
2015-04-17 15:31 ` Jiri Olsa
2015-04-17 20:09 ` Andi Kleen
2015-04-18 13:05 ` Jiri Olsa
2015-04-18 13:12 ` Jiri Olsa
2015-04-14 20:16 ` Andi Kleen
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=1428993665-2133-1-git-send-email-sukadev@linux.vnet.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).