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>,
David Ahern <dsahern@gmail.com>,
Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
Dong Hao <haodong@linux.vnet.ibm.com>
Subject: [PATCH 0/4] perf header: Save and reuse feature information in header (v4)
Date: Fri, 21 Sep 2012 14:16:00 +0900 [thread overview]
Message-ID: <1348204564-1105-1-git-send-email-namhyung@kernel.org> (raw)
Hi,
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.
Thanks,
Namhyung
v3 -> v4:
* rename perf_header_info to perf_session_env (Arnaldo)
v2 -> v3:
* patch 1-3 in v2 merged into tip
* rebased on current acme/perf/core
v1 -> v2:
* not touch EVENT_DESC feature handling
* split out struct perf_header_info
* simplify multi-string handling
* add some cleanup patches
Namhyung Kim (4):
perf header: Add struct perf_session_env
perf header: Add ->process callbacks to most of features
perf header: Use pre-processed session env when printing
perf header: Remove unused @feat arg from ->process callback
tools/perf/util/header.c | 547 +++++++++++++++++++++++++++++++++--------------
tools/perf/util/header.h | 24 +++
2 files changed, 408 insertions(+), 163 deletions(-)
--
1.7.11.4
next reply other threads:[~2012-09-21 5:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 5:16 Namhyung Kim [this message]
2012-09-21 5:16 ` [PATCH 1/4] perf header: Add struct perf_session_env Namhyung Kim
2012-09-21 5:16 ` [PATCH 2/4] perf header: Add ->process callbacks to most of features Namhyung Kim
2012-09-21 5:16 ` [PATCH 3/4] perf header: Use pre-processed session env when printing Namhyung Kim
2012-09-21 5:16 ` [PATCH 4/4] 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=1348204564-1105-1-git-send-email-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=haodong@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=xiaoguangrong@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
all inboxes | Powered by JetHome®