From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 3/3] perf script: Add callindent option
Date: Thu, 23 Jun 2016 13:46:07 -0300 [thread overview]
Message-ID: <20160623164607.GR4213@kernel.org> (raw)
In-Reply-To: <20160623162032.GG25121@tassilo.jf.intel.com>
Em Thu, Jun 23, 2016 at 09:20:32AM -0700, Andi Kleen escreveu:
> > Here I think we should try to make the output more compact, so perhaps
> > we should have some way to ask 'perf script' to show just timestamp
> > deltas from the previous entry, for instance, i.e. replace that 'time'
> > with a new 'delta' -F entry.
>
> Agreed, also have a way to hide the numerical addresses, and some summary
> options to make it easier to use.
>
> However this can be all done as followups later, no need to hold up this basic
> feature series for it.
Yeah, I was just waiting for you to ack it, which you did, thanks, will
process it later today and ship it to Ingo, unless somebody hollers.
- Arnaldo
next prev parent reply other threads:[~2016-06-23 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 13:40 [PATCH V2 0/3] perf script: Add callindent option Adrian Hunter
2016-06-23 13:40 ` [PATCH V2 1/3] perf script: Print sample flags more nicely Adrian Hunter
2016-06-26 10:59 ` [tip:perf/core] " tip-bot for Adrian Hunter
2016-06-23 13:40 ` [PATCH V2 2/3] perf auxtrace: Add option to feed branches to the thread stack Adrian Hunter
2016-06-26 10:59 ` [tip:perf/core] " tip-bot for Adrian Hunter
2016-06-23 13:40 ` [PATCH V2 3/3] perf script: Add callindent option Adrian Hunter
2016-06-23 14:09 ` Arnaldo Carvalho de Melo
2016-06-23 16:20 ` Andi Kleen
2016-06-23 16:46 ` Arnaldo Carvalho de Melo [this message]
2016-06-26 11:00 ` [tip:perf/core] " tip-bot for Adrian Hunter
2016-06-23 16:18 ` [PATCH V2 0/3] " Andi Kleen
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=20160623164607.GR4213@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@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 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).