From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: linux-kernel@vger.kernel.org, acme@redhat.com
Cc: mingo@kernel.org, dsahern@gmail.com, artagnon@gmail.com,
Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
Subject: [PATCH 0/8 V2] Enhancement for perf list.
Date: Mon, 30 Dec 2013 10:26:35 -0500 [thread overview]
Message-ID: <cover.1388416837.git.yangds.fnst@cn.fujitsu.com> (raw)
Hi Arnaldo,
This patchset is for enhancement of perf list version 2.
Ramkumar and David,
The patch [6/8] is from your work 52A8D2DA.7050409@gmail.com, and
I make --raw-dump works as a option for other argument here. Do you mind
I add signed-off-by Ramkumar and signed-off-by David in this patch?
changelog:
-v1
* remove the patch for event_glob
* add a patch [3/8] to add a missing free in print_pmu_events() fucntion.
Dongsheng Yang (8):
perf tools: Make the all print_xxx_event functions to return unsigned
int.
perf tools: Make the print_pmu_events funtion to return unsigned int.
perf tools: free aliases[j] in pmu.c if name_only is true.
perf tools: Improve the message of perf list for unexpected input.
perf tools: Add support of name_only for print_events_type() function.
perf tools: Make --raw-dump work as a proper option for perf list.
perf tools: Fix bug when --raw-dump is not the first arguement for
perf list.
perf tools: Enhancement for perf list with --raw-dump.
tools/perf/builtin-list.c | 32 +++++++++------
tools/perf/util/parse-events.c | 88 ++++++++++++++++++++++++------------------
tools/perf/util/parse-events.h | 8 ++--
tools/perf/util/pmu.c | 15 ++++---
tools/perf/util/pmu.h | 2 +-
5 files changed, 85 insertions(+), 60 deletions(-)
--
1.8.2.1
next reply other threads:[~2013-12-30 2:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 15:26 Dongsheng Yang [this message]
2013-12-30 15:26 ` [PATCH 1/8] perf tools: Make the all print_xxx_event functions to return unsigned int Dongsheng Yang
2013-12-30 15:26 ` [PATCH 2/8] perf tools: Make the print_pmu_events funtion " Dongsheng Yang
2014-01-08 15:10 ` Arnaldo Carvalho de Melo
2014-01-09 14:58 ` Dongsheng Yang
2014-01-09 22:23 ` Dongsheng Yang
2013-12-30 15:26 ` [PATCH 3/8] perf tools: free aliases[j] in pmu.c if name_only is true Dongsheng Yang
2014-01-08 15:12 ` Arnaldo Carvalho de Melo
2014-01-09 14:53 ` Dongsheng Yang
2013-12-30 15:26 ` [PATCH 4/8] perf tools: Improve the message of perf list for unexpected input Dongsheng Yang
2014-01-08 15:16 ` Arnaldo Carvalho de Melo
2014-01-09 14:38 ` Dongsheng Yang
2013-12-30 15:26 ` [PATCH 5/8] perf tools: Add support of name_only for print_events_type() function Dongsheng Yang
2014-01-08 15:19 ` Arnaldo Carvalho de Melo
2014-01-09 14:37 ` Dongsheng Yang
2013-12-30 15:26 ` [PATCH 6/8] perf tools: Make --raw-dump work as a proper option for perf list Dongsheng Yang
2013-12-30 8:09 ` Ramkumar Ramachandra
2014-01-08 15:20 ` Arnaldo Carvalho de Melo
2014-01-08 21:44 ` David Ahern
2014-01-09 14:36 ` Dongsheng Yang
2014-01-10 15:30 ` David Ahern
2014-01-13 21:03 ` Dongsheng Yang
2013-12-30 15:26 ` [PATCH 7/8] perf tools: Fix bug when --raw-dump is not the first arguement " Dongsheng Yang
2013-12-30 15:26 ` [PATCH 8/8] perf tools: Enhancement for perf list with --raw-dump Dongsheng Yang
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=cover.1388416837.git.yangds.fnst@cn.fujitsu.com \
--to=yangds.fnst@cn.fujitsu.com \
--cc=acme@redhat.com \
--cc=artagnon@gmail.com \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome