From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Ahern <daahern@cisco.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 0/2] perf tools: add reference timestamp and use it in time history dump
Date: Thu, 9 Dec 2010 15:18:53 -0200 [thread overview]
Message-ID: <20101209171853.GC13027@ghostprotocols.net> (raw)
In-Reply-To: <1291773285-16254-1-git-send-email-daahern@cisco.com>
Em Tue, Dec 07, 2010 at 06:54:43PM -0700, David Ahern escreveu:
> David Ahern (2):
> perf tools: Add reference timestamp to perf header
> perf tools: Add option to show time history of event samples
>
> tools/perf/builtin-record.c | 8 +++
> tools/perf/builtin-report.c | 131 ++++++++++++++++++++++++++++++++++++++++++-
> tools/perf/util/header.c | 51 +++++++++++++++++
> tools/perf/util/header.h | 3 +
> tools/perf/util/session.c | 26 +++++++++
> 5 files changed, 217 insertions(+), 2 deletions(-)
I'll go to a business trip today/tomorrow, will try to check these while
at the hotel.
Frederic, if you have some time, could you take a look? I touches the
HEADER_FEAT stuff, the feature has a huge potential, merging app
specific logs with perf report output helps correlating counter to app
specific events, great stuff.
I would just love to have at least one more person reviewing this,
thanks,
- Arnaldo
next prev parent reply other threads:[~2010-12-09 17:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 1:54 [PATCH 0/2] perf tools: add reference timestamp and use it in time history dump David Ahern
2010-12-08 1:54 ` [PATCH 1/2] perf tools: Add reference timestamp to perf header David Ahern
2010-12-12 20:16 ` Frederic Weisbecker
2010-12-13 13:15 ` Arnaldo Carvalho de Melo
2010-12-13 16:58 ` Arnaldo Carvalho de Melo
2010-12-13 14:39 ` David S. Ahern
2010-12-13 15:54 ` Frederic Weisbecker
2010-12-13 16:48 ` Arnaldo Carvalho de Melo
2010-12-13 17:09 ` Frederic Weisbecker
2010-12-13 17:11 ` Peter Zijlstra
2010-12-13 17:13 ` Peter Zijlstra
2010-12-13 17:23 ` Frederic Weisbecker
2010-12-13 17:37 ` Peter Zijlstra
2010-12-13 17:50 ` Frederic Weisbecker
2010-12-13 17:15 ` Frederic Weisbecker
2010-12-13 17:18 ` Peter Zijlstra
2010-12-13 17:22 ` Arnaldo Carvalho de Melo
2010-12-13 17:35 ` Peter Zijlstra
2010-12-13 17:43 ` Arnaldo Carvalho de Melo
2010-12-13 17:51 ` Peter Zijlstra
2010-12-13 18:05 ` Frederic Weisbecker
2010-12-13 18:10 ` Peter Zijlstra
2010-12-13 17:47 ` Peter Zijlstra
2010-12-13 17:49 ` David S. Ahern
2010-12-13 17:57 ` Peter Zijlstra
2010-12-13 18:01 ` David S. Ahern
2010-12-13 18:06 ` Peter Zijlstra
2010-12-13 18:20 ` David S. Ahern
2010-12-13 19:08 ` Arnaldo Carvalho de Melo
2010-12-13 19:15 ` David S. Ahern
2010-12-13 19:22 ` Peter Zijlstra
2010-12-13 19:17 ` Peter Zijlstra
2010-12-13 17:48 ` Peter Zijlstra
2010-12-13 17:14 ` Arnaldo Carvalho de Melo
2010-12-13 17:36 ` David S. Ahern
2010-12-13 17:51 ` Arnaldo Carvalho de Melo
2010-12-08 1:54 ` [PATCH 2/2] perf tools: Add option to show time history of event samples David Ahern
2010-12-08 21:06 ` Arnaldo Carvalho de Melo
2010-12-12 21:32 ` Frederic Weisbecker
2010-12-09 17:18 ` Arnaldo Carvalho de Melo [this message]
2010-12-12 21:39 ` [PATCH 0/2] perf tools: add reference timestamp and use it in time history dump 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=20101209171853.GC13027@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=daahern@cisco.com \
--cc=fweisbec@gmail.com \
--cc=linux-perf-users@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.