From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andi Kleen <andi@firstfloor.org>, Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH v4 4/5] perf tools: Support dynamic sort keys for -F/--fields
Date: Thu, 7 Jan 2016 19:54:33 +0900 [thread overview]
Message-ID: <20160107105433.GD5499@danjae.kornet> (raw)
In-Reply-To: <20160107092418.GA28203@krava.brq.redhat.com>
On Thu, Jan 07, 2016 at 10:24:18AM +0100, Jiri Olsa wrote:
> On Thu, Jan 07, 2016 at 09:12:28AM +0900, Namhyung Kim wrote:
> > Now dynamic sort keys are supported for tracepoint events, add it to
> > output fields too.
>
> should we update the doc as well?
The doc lazily says:
-F::
--fields=::
Specify output field - multiple keys can be specified in CSV format.
Following fields are available:
overhead, overhead_sys, overhead_us, overhead_children, sample and period.
Also it can contain any sort key(s).
Thanks,
Namhyung
next prev parent reply other threads:[~2016-01-07 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 0:12 [PATCH v4 1/5] perf tools: Fix sorting of dynamic sort keys Namhyung Kim
2016-01-07 0:12 ` [PATCH v4 2/5] perf tools: Separate hpp->sort callback for " Namhyung Kim
2016-01-07 0:12 ` [PATCH v4 3/5] perf tools: Fix dynamic sort keys to sort properly Namhyung Kim
2016-01-07 0:12 ` [PATCH v4 4/5] perf tools: Support dynamic sort keys for -F/--fields Namhyung Kim
2016-01-07 9:24 ` Jiri Olsa
2016-01-07 10:54 ` Namhyung Kim [this message]
2016-01-07 0:12 ` [PATCH v4 5/5] perf evlist: Add --trace-fields option to show trace fields Namhyung Kim
2016-01-08 17:22 ` Arnaldo Carvalho de Melo
2016-01-09 16:42 ` [tip:perf/core] " tip-bot for Namhyung Kim
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=20160107105433.GD5499@danjae.kornet \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=wangnan0@huawei.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.