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>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCHSET 00/10] perf util: More cleanups on tracepoint handling
Date: Mon, 15 Apr 2013 14:11:28 +0900 [thread overview]
Message-ID: <1366002698-10728-1-git-send-email-namhyung@kernel.org> (raw)
Hello,
It seems some code that handle tracepoint events left unchanged when
they were copied from the trace-cmd. This series tries to cleanup
them by removing unnecessary function calls and variables and filling
up some missing pieces.
It's based on my previous patchset on libtraceevent [1] and contains a
user of the new pevent_set_page_size() API too. :)
You can get this from 'perf/cleanup' branch on my tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
Any comments are welcome, thanks.
Namhyung
[1] https://lkml.org/lkml/2013/4/11/194
Namhyung Kim (10):
perf util: Save page size in a trace file to pevent
perf util: Save long size of traced system
perf util: Make file/host_bigendian variable local
perf util: Skip reading header_event file
perf util: Parse header_page to get proper long size
perf util: Get rid of unused header_page_* variables
perf util: Move latency_format variable to builtin-script.c
perf util: Rename read_*() functions in trace-event-info.c
perf util: No need to call read_trace_init() in tracing_data_header()
perf util: Remove unused enum and macro in trace-event.h
tools/perf/builtin-script.c | 1 +
tools/perf/util/trace-event-info.c | 22 ++++++++---------
tools/perf/util/trace-event-parse.c | 6 -----
tools/perf/util/trace-event-read.c | 49 +++++++++++++++++++++----------------
tools/perf/util/trace-event.h | 15 ------------
5 files changed, 39 insertions(+), 54 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-04-15 5:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 5:11 Namhyung Kim [this message]
2013-04-15 5:11 ` [PATCH 01/10] perf util: Save page size in a trace file to pevent Namhyung Kim
2013-04-15 5:11 ` [PATCH 02/10] perf util: Save long size of traced system Namhyung Kim
2013-04-15 5:11 ` [PATCH 03/10] perf util: Make file/host_bigendian variable local Namhyung Kim
2013-04-15 5:11 ` [PATCH 04/10] perf util: Skip reading header_event file Namhyung Kim
2013-04-15 5:11 ` [PATCH 05/10] perf util: Parse header_page to get proper long size Namhyung Kim
2013-04-17 3:59 ` [PATCH v2 " Namhyung Kim
2013-04-15 5:11 ` [PATCH 06/10] perf util: Get rid of unused header_page_* variables Namhyung Kim
2013-04-15 5:11 ` [PATCH 07/10] perf util: Move latency_format variable to builtin-script.c Namhyung Kim
2013-04-15 5:11 ` [PATCH 08/10] perf util: Rename read_*() functions in trace-event-info.c Namhyung Kim
2013-04-15 5:11 ` [PATCH 09/10] perf util: No need to call read_trace_init() in tracing_data_header() Namhyung Kim
2013-04-15 5:11 ` [PATCH 10/10] perf util: Remove unused enum and macro in trace-event.h 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=1366002698-10728-1-git-send-email-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.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®