From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Ahern <dsahern@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Namhyung Kim <namhyung@kernel.org>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 0/2] perf tools: Add --header/--header-only options
Date: Tue, 10 Dec 2013 08:42:18 -0300 [thread overview]
Message-ID: <20131210114218.GH8098@ghostprotocols.net> (raw)
In-Reply-To: <52A65169.2030705@gmail.com>
Em Mon, Dec 09, 2013 at 04:25:29PM -0700, David Ahern escreveu:
> [Added Stephane given that he added the header output]
Yeah, I added him to the CC list in the patch when I merged it, Ingo had
asked me to do this quite some time ago, I also usually did:
$ perf report | grep -v ^#
When looking for the first few entries in a profile.
I think that with Namhyung's improvement to the man page + the single
line stating that --header should be used to get the previous behavior
we are ok, no?
> On 12/9/13, 3:02 AM, Jiri Olsa wrote:
> >Currently the perf.data header is always displayed for stdio
> >output, which is no always useful.
> >Disabling header information by default and adding following
> >options to control header output:
> > --header - display header information (old default)
> > --header-only - display header information only w/o further
> > processing.
> I've been getting annoyed but that as well. Very useful on the first
> run; overhead after that.
> Acked-by: David Ahern <dsahern@gmail.com>
I'll add this since I'll have to reprocess the last batch due to the
dso__delete problem.
- Arnaldo
next prev parent reply other threads:[~2013-12-10 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 10:02 [PATCH 0/2] perf tools: Add --header/--header-only options Jiri Olsa
2013-12-09 10:02 ` [PATCH 1/2] perf report: " Jiri Olsa
2013-12-10 0:12 ` Namhyung Kim
2013-12-10 10:12 ` Jiri Olsa
2013-12-11 11:06 ` [tip:perf/core] " tip-bot for Jiri Olsa
2013-12-09 10:02 ` [PATCH 2/2] perf script: " Jiri Olsa
2013-12-11 11:06 ` [tip:perf/core] " tip-bot for Jiri Olsa
2013-12-09 23:25 ` [PATCH 0/2] perf tools: " David Ahern
2013-12-10 11:42 ` Arnaldo Carvalho de Melo [this message]
2013-12-10 0:06 ` Namhyung Kim
2013-12-10 10:11 ` Jiri Olsa
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=20131210114218.GH8098@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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 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.