From: David Ahern <dsahern@gmail.com>
To: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, peterz@infradead.org, fweisbec@gmail.com,
tglx@linutronix.de
Cc: acme@ghostprotocols.net, paulus@samba.org
Subject: Re: [PATCH 0/6] Add time-of-day option to perf events
Date: Tue, 14 Jun 2011 12:42:12 -0600 [thread overview]
Message-ID: <4DF7AB84.3080000@gmail.com> (raw)
In-Reply-To: <1307490806-24548-1-git-send-email-dsahern@gmail.com>
ping?
On 06/07/2011 05:53 PM, David Ahern wrote:
> Another attempt at printing time-of-day strings on perf events - this
> time with tracepoints in the timekeeping code to catch updates to
> xtime.
>
> David Ahern (6):
> trace: add tracepoints to timekeeping code - xtime changes
> perf utils: export parse_single_tracepoint_event
> perf: add reference time event
> perf record: add time-of-day option
> perf script: pass trace event to print_trace_event
> perf script: add time-of-day option for displaying events
>
> include/trace/events/timekeeping.h | 43 ++++++++
> kernel/time/timekeeping.c | 8 ++
> tools/perf/Documentation/perf-record.txt | 3 +
> tools/perf/Documentation/perf-script.txt | 8 ++-
> tools/perf/builtin-record.c | 102 +++++++++++++++++++-
> tools/perf/builtin-script.c | 157 +++++++++++++++++++++++++++++-
> tools/perf/util/event.c | 1 +
> tools/perf/util/event.h | 8 ++
> tools/perf/util/parse-events.c | 13 +--
> tools/perf/util/parse-events.h | 12 +++
> tools/perf/util/session.c | 4 +
> tools/perf/util/session.h | 3 +-
> tools/perf/util/trace-event-parse.c | 12 +--
> tools/perf/util/trace-event.h | 2 +-
> 14 files changed, 350 insertions(+), 26 deletions(-)
> create mode 100644 include/trace/events/timekeeping.h
>
prev parent reply other threads:[~2011-06-14 18:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 23:53 [PATCH 0/6] Add time-of-day option to perf events David Ahern
2011-06-07 23:55 ` [PATCH 1/6] trace: add tracepoints to timekeeping code - xtime changes David Ahern
2011-06-17 13:23 ` Frederic Weisbecker
2011-06-17 14:13 ` David Ahern
2011-06-17 14:19 ` Frederic Weisbecker
2011-08-15 4:03 ` David Ahern
2011-06-07 23:55 ` [PATCH 2/6] perf utils: export parse_single_tracepoint_event David Ahern
2011-06-07 23:55 ` [PATCH 3/6] perf: add reference time event David Ahern
2011-06-17 13:32 ` Frederic Weisbecker
2011-06-17 14:04 ` David Ahern
2011-06-17 14:17 ` Frederic Weisbecker
2011-06-17 14:28 ` David Ahern
2011-07-11 4:20 ` David Ahern
2011-07-12 14:30 ` Frederic Weisbecker
2011-07-12 16:35 ` David Ahern
2011-07-12 17:03 ` Frederic Weisbecker
2011-08-04 15:10 ` David Ahern
[not found] ` <20110808193033.GA2744@ghostprotocols.net>
2011-08-15 4:06 ` David Ahern
2011-06-07 23:56 ` [PATCH 4/6] perf record: add time-of-day option David Ahern
2011-06-17 14:14 ` Frederic Weisbecker
2011-06-17 14:23 ` David Ahern
2011-06-17 15:15 ` Frederic Weisbecker
2011-08-15 4:24 ` David Ahern
2011-06-07 23:56 ` [PATCH 5/6] perf script: pass trace event to print_trace_event David Ahern
2011-06-07 23:56 ` [PATCH 6/6] perf script: add time-of-day option for displaying events David Ahern
2011-06-14 18:42 ` David Ahern [this message]
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=4DF7AB84.3080000@gmail.com \
--to=dsahern@gmail.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).