From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Andi Kleen <ak@linux.intel.com>
Cc: Tim Chen <tim.c.chen@linux.intel.com>,
David Ahern <dsahern@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: Does perf inject preserve call chain data?
Date: Mon, 11 Jun 2012 18:59:12 -0300 [thread overview]
Message-ID: <20120611215912.GA3897@infradead.org> (raw)
In-Reply-To: <4FD63C52.4090003@linux.intel.com>
Em Mon, Jun 11, 2012 at 11:43:30AM -0700, Andi Kleen escreveu:
> ># perf top -a -G sleep 5
> >
> >Where it would figure out that since a workload was specified, it should
> >just not be refreshing the screen every N seconds but wait till the
> >workload to finish and then present the results, without setting up any
> >perf.data files.
>
> But top does not generate email'able ASCII format like perf report
> does, doesn't it?
http://git.kernel.org/?p=linux/kernel/git/acme/linux.git;a=commit;h=a78e5b82e99d8d284afc012ef015ef3332153aaf
perf hists browser: Implement printing snapshots to files
To avoid having to resort to --stdio, that expands everything, instead
allow the user to go on expanding the relevant callchains and then press
'P' to print that view.
As the hists browser is used for both static (report) and dynamic (top)
views, it prints to a 'perf.hists.N' sequence, i.e. multiple snapshots
can be taken in report and top.
</>
On a v3.6 kernel near you, together with:
http://git.kernel.org/?p=linux/kernel/git/acme/linux.git;a=commit;h=bd622d64e4bb0d10e8f0c2df4de9303ee415ffae
:-)
- Arnaldo
next prev parent reply other threads:[~2012-06-11 21:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 18:49 Does perf inject preserve call chain data? Tim Chen
2012-05-22 21:58 ` David Ahern
2012-06-08 14:38 ` Arnaldo Carvalho de Melo
2012-06-08 16:44 ` Tim Chen
2012-06-08 17:13 ` David Ahern
2012-06-08 17:17 ` Tim Chen
2012-06-08 19:52 ` Andi Kleen
2012-06-09 16:05 ` Arnaldo Carvalho de Melo
2012-06-11 18:43 ` Andi Kleen
2012-06-11 19:11 ` David Ahern
2012-06-11 21:59 ` Arnaldo Carvalho de Melo [this message]
2012-06-11 22:11 ` Andi Kleen
2012-06-12 0:02 ` Arnaldo Carvalho de Melo
2012-06-11 18:23 ` David Ahern
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=20120611215912.GA3897@infradead.org \
--to=acme@ghostprotocols.net \
--cc=ak@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@linux.intel.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 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.