All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Tim Chen <tim.c.chen@linux.intel.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 13:11:51 -0600	[thread overview]
Message-ID: <4FD642F7.3060201@gmail.com> (raw)
In-Reply-To: <4FD63C52.4090003@linux.intel.com>

On 6/11/12 12:43 PM, Andi Kleen wrote:
>
>
>> # 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?


perf top --stdio ...


  reply	other threads:[~2012-06-11 19:11 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 [this message]
2012-06-11 21:59                 ` Arnaldo Carvalho de Melo
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=4FD642F7.3060201@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=ak@linux.intel.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.