public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>,
	Namhyung Kim <namhyung.kim@lge.com>,
	LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
	David Ahern <dsahern@gmail.com>, Andi Kleen <andi@firstfloor.org>
Subject: Re: [RFC 00/10] perf report: Add -F option for specifying output fields
Date: Tue, 4 Mar 2014 08:19:34 +0100	[thread overview]
Message-ID: <20140304071934.GA23148@gmail.com> (raw)
In-Reply-To: <1393900936-22977-1-git-send-email-namhyung@kernel.org>


* Namhyung Kim <namhyung@kernel.org> wrote:

> Hello,
> 
> This is a patchset implementing -F/--field option to setup output
> field/column as Ingo requested.
> 
> The -F option can receive any sort keys that -s option recognize, plus
> following fields (name can be changed):
> 
>   overhead, overhead_sys, overhead_us, sample, period
> 
> The overhead_guest_sys and overhead_guest_us might be avaiable when
> you profile guest machines.
> 
> Output will be sorted by in order of fields and sort keys passed by 
> -s option will be added to the output field list automatically.  If 
> you want to change the order of sorting you can give -s option in 
> addition to -F option.  To support old behavior, it'll also prepend 
> 'overhead' field to the sort keys unless you give -F option 
> explicitly.

Very nice!

For the concept:

  Acked-by: Ingo Molnar <mingo@kernel.org>

Thanks,

	Ingo

      parent reply	other threads:[~2014-03-04  7:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  2:42 [RFC 00/10] perf report: Add -F option for specifying output fields Namhyung Kim
2014-03-04  2:42 ` [PATCH 01/10] perf tools: Add ->cmp(), ->collapse() and ->sort() to perf_hpp_fmt Namhyung Kim
2014-03-04  2:42 ` [PATCH 02/10] perf tools: Convert sort entries to hpp formats Namhyung Kim
2014-03-04  2:42 ` [PATCH 03/10] perf tools: Use hpp formats to sort hist entries Namhyung Kim
2014-03-04  2:42 ` [PATCH 04/10] perf tools: Support event grouping in hpp ->sort() Namhyung Kim
2014-03-04  2:42 ` [PATCH 05/10] perf tools: Use hpp formats to sort final output Namhyung Kim
2014-03-04  2:42 ` [PATCH 06/10] perf tools: Consolidate output field handling to hpp format routines Namhyung Kim
2014-03-04  2:42 ` [PATCH 07/10] perf ui: Get rid of callback from __hpp__fmt() Namhyung Kim
2014-03-04  2:42 ` [PATCH 08/10] perf tools: Allow hpp fields to be sort keys Namhyung Kim
2014-03-04  2:42 ` [PATCH 09/10] perf report: Add -F option to specify output fields Namhyung Kim
2014-03-04  2:42 ` [PATCH 10/10] perf tools: Add ->sort() member to struct sort_entry Namhyung Kim
2014-03-04  2:45 ` [RFC 00/10] perf report: Add -F option for specifying output fields Namhyung Kim
2014-03-04  7:19 ` Ingo Molnar [this message]

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=20140304071934.GA23148@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=andi@firstfloor.org \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung.kim@lge.com \
    --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