From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH 1/2] perf report: Add --header/--header-only options
Date: Tue, 10 Dec 2013 09:12:10 +0900 [thread overview]
Message-ID: <87ppp5lg2t.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1386583370-1699-2-git-send-email-jolsa@redhat.com> (Jiri Olsa's message of "Mon, 9 Dec 2013 11:02:49 +0100")
On Mon, 9 Dec 2013 11:02:49 +0100, 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, forces stdio output
>
[SNIP]
> +--header
> + Show perf.data header.
This explanation looks too terse. How about this?
Show header information in the perf.data file. This includes
various information like hostname, os and perf version, cpu/mem
info, perf command line, event list and so on. Currently only
--stdio output supports this feature.
Thanks,
Namhyung
> +
> +--header-only
> + Show only perf.data header (forces --stdio).
> +
> SEE ALSO
> --------
> linkperf:perf-stat[1], linkperf:perf-annotate[1]
next prev parent reply other threads:[~2013-12-10 0:12 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 [this message]
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
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=87ppp5lg2t.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox