From: David Ahern <daahern@cisco.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
acme@ghostprotocols.net, peterz@infradead.org, paulus@samba.org,
tglx@linutronix.de
Subject: Re: [PATCH 0/4] perf events: Add realtime clock event and timehist option -v2
Date: Tue, 22 Feb 2011 01:07:17 -0700 [thread overview]
Message-ID: <4D636EB5.3030605@cisco.com> (raw)
In-Reply-To: <20110222074158.GA32322@elte.hu>
On 02/22/11 00:41, Ingo Molnar wrote:
>
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
>
>> perf-script is not new, it was there in november already, although named perf
>> trace at that time.
>
> Yes.
>
> The new 'perf trace' utility - which might be the straightforward 'report a trace'
> utility that David is looking for is still WIP and can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git tmp.perf/trace
>
> Warning: the code is stale and needs much more work to become mergable. But
> displaying GTOD timestamps is very much something that looks sensible in the 'perf
> trace' context as well.
Ok. I'll look at moving the timehist option from perf-report to perf-script.
David
>
> Thanks,
>
> Ingo
prev parent reply other threads:[~2011-02-22 8:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 21:02 [PATCH 0/4] perf events: Add realtime clock event and timehist option -v2 David Ahern
2011-02-21 21:02 ` [PATCH 1/4] perf events: Introduce realtime clock event David Ahern
2011-02-21 21:02 ` [PATCH 2/4] perf events: plumbing for PERF_SAMPLE_READ and read_format David Ahern
2011-02-21 21:02 ` [PATCH 3/4] perf events: add timehist option to record and report David Ahern
2011-02-21 21:02 ` [PATCH 4/4] perf stat: treat realtime-clock as nsec counter David Ahern
2011-02-21 21:37 ` [PATCH 0/4] perf events: Add realtime clock event and timehist option -v2 Frederic Weisbecker
2011-02-21 21:41 ` David Ahern
2011-02-21 21:55 ` Frederic Weisbecker
2011-02-21 22:09 ` David Ahern
2011-02-21 22:21 ` Frederic Weisbecker
2011-02-22 1:16 ` David Ahern
2011-02-22 2:50 ` Frederic Weisbecker
2011-02-22 7:41 ` Ingo Molnar
2011-02-22 8:07 ` 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=4D636EB5.3030605@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).