mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
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 11:12:02 +0100	[thread overview]
Message-ID: <20131210101202.GB8108@krava.brq.redhat.com> (raw)
In-Reply-To: <87ppp5lg2t.fsf@sejong.aot.lge.com>

On Tue, Dec 10, 2013 at 09:12:10AM +0900, Namhyung Kim wrote:
> 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.

sounds good, I will use it

thanks,
jirka

  reply	other threads:[~2013-12-10 10: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: " 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 [this message]
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=20131210101202.GB8108@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®