From: Namhyung Kim <namhyung@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Andi Kleen <andi@firstfloor.org>,
Don Zickus <dzickus@redhat.com>
Subject: Re: [PATCH 04/20] perf tools: Support event grouping in hpp ->sort()
Date: Fri, 16 May 2014 15:19:19 +0900 [thread overview]
Message-ID: <87mweikzyw.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20140515114315.GB4009@krava.brq.redhat.com> (Jiri Olsa's message of "Thu, 15 May 2014 13:43:15 +0200")
Hi Jiri,
On Thu, 15 May 2014 13:43:15 +0200, Jiri Olsa wrote:
> On Mon, May 12, 2014 at 03:28:37PM +0900, Namhyung Kim wrote:
>
> SNIP
>
>> +static int __hpp__sort(struct hist_entry *a, struct hist_entry *b,
>> + hpp_field_fn get_field)
>> +{
>> + s64 ret;
>> + int i, nr_members;
>> + struct perf_evsel *evsel;
>> + struct hist_entry *pair;
>> + u64 *fields_a, *fields_b;
>> +
>> + ret = field_cmp(get_field(a), get_field(b));
>> + if (ret || !symbol_conf.event_group)
>> + return ret;
>> +
>> + evsel = hists_to_evsel(a->hists);
>> + if (!perf_evsel__is_group_event(evsel))
>> + return ret;
>> +
>> + nr_members = evsel->nr_members;
>> + fields_a = calloc(sizeof(*fields_a), nr_members);
>> + fields_b = calloc(sizeof(*fields_b), nr_members);
>> +
>> + if (!fields_a || !fields_b)
>> + goto out;
>> +
>> + list_for_each_entry(pair, &a->pairs.head, pairs.node) {
>> + evsel = hists_to_evsel(pair->hists);
>> + fields_a[perf_evsel__group_idx(evsel)] = get_field(pair);
>> + }
>> +
>> + list_for_each_entry(pair, &b->pairs.head, pairs.node) {
>> + evsel = hists_to_evsel(pair->hists);
>> + fields_b[perf_evsel__group_idx(evsel)] = get_field(pair);
>> + }
>> +
>> + for (i = 1; i < nr_members; i++) {
>> + ret = fields_a[i] - fields_b[i];
>
> should we call here ^^^call field_cmp ?
Right! Will fix.
Thanks,
Namhyung
next prev parent reply other threads:[~2014-05-16 6:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 6:28 [PATCHSET 00/20] perf report: Add -F option for specifying output fields (v5) Namhyung Kim
2014-05-12 6:28 ` [PATCH 01/20] perf tools: Add ->cmp(), ->collapse() and ->sort() to perf_hpp_fmt Namhyung Kim
2014-05-12 6:28 ` [PATCH 02/20] perf tools: Convert sort entries to hpp formats Namhyung Kim
2014-05-12 6:28 ` [PATCH 03/20] perf tools: Use hpp formats to sort hist entries Namhyung Kim
2014-05-12 6:28 ` [PATCH 04/20] perf tools: Support event grouping in hpp ->sort() Namhyung Kim
2014-05-15 11:43 ` Jiri Olsa
2014-05-16 6:19 ` Namhyung Kim [this message]
2014-05-12 6:28 ` [PATCH 05/20] perf tools: Use hpp formats to sort final output Namhyung Kim
2014-05-12 6:28 ` [PATCH 06/20] perf tools: Consolidate output field handling to hpp format routines Namhyung Kim
2014-05-15 12:07 ` Jiri Olsa
2014-05-16 6:23 ` Namhyung Kim
2014-05-15 12:11 ` Jiri Olsa
2014-05-16 6:26 ` Namhyung Kim
2014-05-12 6:28 ` [PATCH 07/20] perf ui: Get rid of callback from __hpp__fmt() Namhyung Kim
2014-05-12 6:28 ` [PATCH 08/20] perf tools: Allow hpp fields to be sort keys Namhyung Kim
2014-05-15 12:51 ` Jiri Olsa
2014-05-16 6:30 ` Namhyung Kim
2014-05-19 5:58 ` Namhyung Kim
2014-05-15 13:07 ` Jiri Olsa
2014-05-16 6:29 ` Namhyung Kim
2014-05-12 6:28 ` [PATCH 09/20] perf tools: Consolidate management of default sort orders Namhyung Kim
2014-05-15 13:01 ` Jiri Olsa
2014-05-12 6:28 ` [PATCH 10/20] perf tools: Call perf_hpp__init() before setting up GUI browsers Namhyung Kim
2014-05-12 6:28 ` [PATCH 11/20] perf report: Add -F option to specify output fields Namhyung Kim
2014-05-15 13:17 ` Jiri Olsa
2014-05-16 6:33 ` Namhyung Kim
2014-05-19 6:02 ` Namhyung Kim
2014-05-12 6:28 ` [PATCH 12/20] perf tools: Add ->sort() member to struct sort_entry Namhyung Kim
2014-05-15 13:43 ` Jiri Olsa
2014-05-16 6:40 ` Namhyung Kim
2014-05-12 6:28 ` [PATCH 13/20] perf report/tui: Fix a bug when --fields/sort is given Namhyung Kim
2014-05-12 6:28 ` [PATCH 14/20] perf top: Add --fields option to specify output fields Namhyung Kim
2014-05-12 6:28 ` [PATCH 15/20] perf diff: Add missing setup_output_field() Namhyung Kim
2014-05-15 13:47 ` Jiri Olsa
2014-05-12 6:28 ` [PATCH 16/20] perf tools: Skip elided sort entries Namhyung Kim
2014-05-12 6:28 ` [PATCH 17/20] perf hists: Reset width of output fields with header length Namhyung Kim
2014-05-12 6:28 ` [PATCH 18/20] perf tools: Introduce reset_output_field() Namhyung Kim
2014-05-12 6:28 ` [PATCH 19/20] perf tests: Factor out print_hists_*() Namhyung Kim
2014-05-12 6:28 ` [PATCH 20/20] perf tests: Add a testcase for histogram output sorting Namhyung Kim
2014-05-15 13:54 ` [PATCHSET 00/20] perf report: Add -F option for specifying output fields (v5) Jiri Olsa
2014-05-16 6:43 ` Namhyung Kim
-- strict thread matches above, loose matches on Subject: below --
2014-05-19 6:25 [PATCHSET 00/20] perf report: Add -F option for specifying output fields (v6) Namhyung Kim
2014-05-19 6:25 ` [PATCH 04/20] perf tools: Support event grouping in hpp ->sort() 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=87mweikzyw.fsf@sejong.aot.lge.com \
--to=namhyung@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=dzickus@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--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