From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/7] perf header: Save and reuse feature information in header (v2)
Date: Wed, 5 Sep 2012 14:02:46 +0900 [thread overview]
Message-ID: <1346821373-31621-1-git-send-email-namhyung@kernel.org> (raw)
Hi,
This is a v2 of my perf header cleanup series. The v1 can be found
here [1].
Currently the perf header information is used only at initial setup
time and discarded. If it's saved we could reuse the information for
various purpose in the future.
The patch 1-3 are cleanups so that they can be applied independently.
I also put the series on my tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git perf/header-v2
Any comments are welcome, thanks.
Namhyung
[1] https://lkml.org/lkml/2012/7/21/75
v1 -> v2:
* not touch EVENT_DESC feature handling
* split out struct perf_header_info
* simplify multi-string handling
* add some cleanup patches
Namhyung Kim (7):
perf header: Use evlist->nr_entries on write_event_desc()
perf header: Set tracepoint event name only if not set
perf header: Swap pmu mapping numbers if needed
perf header: Add struct perf_header_info
perf header: Add ->process callbacks to most of features
perf header: Use pre-processed header info when printing
perf header: Remove unused @feat arg from ->process callback
tools/perf/util/header.c | 528 +++++++++++++++++++++++++++++++++--------------
tools/perf/util/header.h | 24 +++
2 files changed, 393 insertions(+), 159 deletions(-)
--
1.7.11.4
next reply other threads:[~2012-09-05 5:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 5:02 Namhyung Kim [this message]
2012-09-05 5:02 ` [PATCH 1/7] perf header: Use evlist->nr_entries on write_event_desc() Namhyung Kim
2012-09-07 6:06 ` [tip:perf/core] perf header: Use evlist-> nr_entries " tip-bot for Namhyung Kim
2012-09-05 5:02 ` [PATCH 2/7] perf header: Set tracepoint event name only if not set Namhyung Kim
2012-09-07 6:07 ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-09-05 5:02 ` [PATCH 3/7] perf header: Swap pmu mapping numbers if needed Namhyung Kim
2012-09-07 6:08 ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-09-05 5:02 ` [PATCH 4/7] perf header: Add struct perf_header_info Namhyung Kim
2012-09-05 5:02 ` [PATCH 5/7] perf header: Add ->process callbacks to most of features Namhyung Kim
2012-09-05 5:02 ` [PATCH 6/7] perf header: Use pre-processed header info when printing Namhyung Kim
2012-09-05 5:02 ` [PATCH 7/7] perf header: Remove unused @feat arg from ->process callback Namhyung Kim
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=1346821373-31621-1-git-send-email-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®