From: David Ahern <daahern@cisco.com>
To: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: acme@ghostprotocols.net, mingo@elte.hu, peterz@infradead.org,
fweisbec@gmail.com, paulus@samba.org, tglx@linutronix.de,
David Ahern <daahern@cisco.com>
Subject: [PATCH 0/3] perf script: add support for S/W events and H/W based profiling
Date: Wed, 2 Mar 2011 10:29:17 -0700 [thread overview]
Message-ID: <1299086960-26964-1-git-send-email-daahern@cisco.com> (raw)
Pulling this part of the time-of-day series since the functionality is
independent.
David Ahern (3):
perf script: change process_event prototype
perf script: prepare to handle more than tracepoint events
perf script: dump software events and samples from hardware-based
profiling
tools/perf/Documentation/perf-script.txt | 19 +++
tools/perf/builtin-script.c | 118 ++++++++++++++-----
.../util/scripting-engines/trace-event-python.c | 20 +++-
tools/perf/util/session.c | 113 +++++++++++++++++++
tools/perf/util/session.h | 6 +
tools/perf/util/trace-event-parse.c | 4 +-
tools/perf/util/trace-event-scripting.c | 8 +-
tools/perf/util/trace-event.h | 10 +-
8 files changed, 253 insertions(+), 45 deletions(-)
--
1.7.4
next reply other threads:[~2011-03-02 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 17:29 David Ahern [this message]
2011-03-02 17:29 ` [PATCH 1/3] perf script: change process_event prototype David Ahern
2011-03-03 2:40 ` Frederic Weisbecker
2011-03-03 14:11 ` David Ahern
2011-03-03 17:07 ` Frederic Weisbecker
2011-03-02 17:29 ` [PATCH 2/3] perf script: prepare to handle more than tracepoint events David Ahern
2011-03-02 17:29 ` [PATCH 3/3] perf script: dump software events and samples from hardware-based profiling David Ahern
2011-03-03 3:05 ` Frederic Weisbecker
2011-03-03 14:20 ` David Ahern
2011-03-03 17:19 ` Frederic Weisbecker
2011-03-03 17:30 ` David Ahern
2011-03-03 18:06 ` Frederic Weisbecker
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=1299086960-26964-1-git-send-email-daahern@cisco.com \
--to=daahern@cisco.com \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).