From: Feng Tang <feng.tang@intel.com>
To: acme@redhat.com
Cc: mingo@elte.hu, a.p.zijlstra@chello.nl, andi@firstfloor.org,
namhyung@kernel.org, dsahern@gmail.com,
linux-kernel@vger.kernel.org, Feng Tang <feng.tang@intel.com>
Subject: [PATCH 0/7] perf ui/browser: Add browser for perf script
Date: Mon, 3 Sep 2012 16:14:26 +0800 [thread overview]
Message-ID: <1346660073-20279-1-git-send-email-feng.tang@intel.com> (raw)
Hi Arnaldo and all,
This is a patch set mainly to add a browser for perf script, which
will be integrated into the main hists and annotation browser.
Patch 1-4 are some preparation for adding the script
patch 5 introduce the script browser
patch 6-7 integrate the browser to hists browser and annotation browser
The patches are on top of current perf/core branch of your git tree.
Please help to review, thanks
Feng
-----------------------
Feng Tang (7):
perf symbols: Filter samples with unresolved symbol when "--symbols"
option is used
perf scripts: Add --symbols option to handle specific symbols
perf scripts: Add event_analyzing_sample-record/report
perf scripts: Export a find_scripts() function
perf ui/browser: Add a browser for perf script
perf ui/browser: Integrate script browser into annotation browser
perf ui/browser: Integrate script browser into main hists browser
tools/perf/Makefile | 5 +
tools/perf/builtin-script.c | 49 ++++++
tools/perf/builtin.h | 1 +
.../python/bin/event_analyzing_sample-record | 8 +
.../python/bin/event_analyzing_sample-report | 3 +
tools/perf/ui/browsers/annotate.c | 8 +
tools/perf/ui/browsers/hists.c | 39 +++++
tools/perf/ui/browsers/scripts.c | 159 ++++++++++++++++++++
tools/perf/ui/browsers/scripts.h | 5 +
tools/perf/util/event.c | 5 +-
10 files changed, 280 insertions(+), 2 deletions(-)
create mode 100644 tools/perf/scripts/python/bin/event_analyzing_sample-record
create mode 100644 tools/perf/scripts/python/bin/event_analyzing_sample-report
create mode 100644 tools/perf/ui/browsers/scripts.c
create mode 100644 tools/perf/ui/browsers/scripts.h
next reply other threads:[~2012-09-03 8:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 8:14 Feng Tang [this message]
2012-09-03 8:14 ` [PATCH 1/7] perf symbols: Filter samples with unresolved symbol when "--symbols" option is used Feng Tang
2012-09-03 8:14 ` [PATCH 2/7] perf scripts: Add --symbols option to handle specific symbols Feng Tang
2012-09-03 8:14 ` [PATCH 3/7] perf scripts: Add event_analyzing_sample-record/report Feng Tang
2012-09-03 8:14 ` [PATCH 4/7] perf scripts: Export a find_scripts() function Feng Tang
2012-09-04 1:09 ` Namhyung Kim
2012-09-04 1:34 ` Namhyung Kim
2012-09-03 8:14 ` [PATCH 5/7] perf ui/browser: Add a browser for perf script Feng Tang
2012-09-04 1:57 ` Namhyung Kim
2012-09-04 9:13 ` Feng Tang
2012-09-05 0:33 ` Namhyung Kim
2012-09-03 8:14 ` [PATCH 6/7] perf ui/browser: Integrate script browser into annotation browser Feng Tang
2012-09-03 8:14 ` [PATCH 7/7] perf ui/browser: Integrate script browser into main hists browser Feng Tang
2012-09-04 0:50 ` [PATCH 0/7] perf ui/browser: Add browser for perf script 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=1346660073-20279-1-git-send-email-feng.tang@intel.com \
--to=feng.tang@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).