From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: Tom Zanussi <tzanussi@gmail.com>,
linux-kernel@vger.kernel.org, fweisbec@gmail.com,
rostedt@goodmis.org, k-keiichi@bx.jp.nec.com
Subject: Re: [RFC PATCH 0/7] perf: 'live mode'
Date: Sat, 27 Mar 2010 20:00:55 -0300 [thread overview]
Message-ID: <20100327230055.GJ23594@ghostprotocols.net> (raw)
In-Reply-To: <20100304111856.GE21977@elte.hu>
Em Thu, Mar 04, 2010 at 12:18:56PM +0100, Ingo Molnar escreveu:
> * Tom Zanussi <tzanussi@gmail.com> wrote:
>
> > Currently, a perf session entails two steps: first 'perf record' or 'perf
> > trace record' records the perf data to disk, then 'perf report' or 'perf
> > trace report' reads the saved data from disk and reports the results.
> >
> > This experimental patchset makes some changes to perf that instead allow the
> > perf data to be piped directly from the record step to the report step,
> > without ever touching the disk.
>
> Very nice!
>
> > Obviously, it would be better to have a real top-like display for these
> > rather than a continuously scrolling mode like this, and of course it will
> > be much more useful once we get the syscall name injection events going (the
> > column on the left shows syscall numbers only).
>
> It's still useful for ad-hoc tracing!
>
> Side-note, it might make sense to expose the 'clear' escape sequence somehow
> in an easy fashion:
>
> ^[[H^[[2J
>
> to make it non-scrolling ;-) via a pre-provided method.
>
> > There are some rough edges and inefficiencies, and I guess 'event injection'
> > may be a better way to do this in the end, but it seems to work pretty well
> > already, and I think it shows how useful such a capability can be.
>
> I'm all for it. Frederic, Steve, what do you think?
ITs really nice indeed, I'm reviewing the patches and will test them
after weekend, it fits nicely with the idea of unifying top and report,
i.e. the refresh thing he mentions could do the decay as well if a
parameter is set.
Thnaks Frederic for pointing this patchset to me.
Great work!
- Arnaldo
next prev parent reply other threads:[~2010-03-27 23:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 7:05 [RFC PATCH 0/7] perf: 'live mode' Tom Zanussi
2010-03-03 7:05 ` [RFC PATCH 1/7] perf: introduce special handling for pipe input/output Tom Zanussi
2010-03-03 7:05 ` [RFC PATCH 2/7] perf: add pipe-specific header read/write and event processing code Tom Zanussi
2010-03-27 3:14 ` Frederic Weisbecker
2010-03-27 22:57 ` Arnaldo Carvalho de Melo
2010-03-27 23:05 ` Arnaldo Carvalho de Melo
2010-03-27 23:12 ` Frederic Weisbecker
2010-03-28 0:15 ` Arnaldo Carvalho de Melo
2010-03-03 7:05 ` [RFC PATCH 3/7] perf: convert perf header attrs into attr events Tom Zanussi
2010-03-03 7:05 ` [RFC PATCH 4/7] perf: convert perf event types into event type events Tom Zanussi
2010-03-03 7:05 ` [RFC PATCH 5/7] perf: convert perf tracing data into a tracing_data event Tom Zanussi
2010-03-03 7:05 ` [RFC PATCH 6/7] perf: convert perf header build_ids into build_id events Tom Zanussi
2010-03-03 7:05 ` [RFC PATCH 7/7] perf trace/scripting: rwtop and sctop scripts Tom Zanussi
2010-03-04 11:18 ` [RFC PATCH 0/7] perf: 'live mode' Ingo Molnar
2010-03-27 23:00 ` Arnaldo Carvalho de Melo [this message]
2010-03-28 5:04 ` Tom Zanussi
2010-03-27 0:57 ` 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=20100327230055.GJ23594@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=k-keiichi@bx.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
/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