From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: 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: [PATCH v4 2/5] perf tools: Separate hpp->sort callback for dynamic sort keys
Date: Thu, 7 Jan 2016 09:12:26 +0900 [thread overview]
Message-ID: <1452125549-1511-2-git-send-email-namhyung@kernel.org> (raw)
In-Reply-To: <1452125549-1511-1-git-send-email-namhyung@kernel.org>
The ->sort callback is used for final output sorting. As it's called
after processing all hist entries, it doesn't need to update dynamic
length anymore. Also it needs additional handling to sort them
properly (which is the topic of next patch).
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
---
tools/perf/util/sort.c | 26 +++++++++++++++++++++++++-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/sort.c b/tools/perf/util/sort.c
index 425097d2a1cd..e8a5cdee3f0d 100644
--- a/tools/perf/util/sort.c
+++ b/tools/perf/util/sort.c
@@ -1798,6 +1798,30 @@ static int64_t __sort__hde_cmp(struct perf_hpp_fmt *fmt,
return memcmp(b->raw_data + offset, a->raw_data + offset, size);
}
+static int64_t __sort__hde_sort(struct perf_hpp_fmt *fmt,
+ struct hist_entry *a, struct hist_entry *b)
+{
+ struct hpp_dynamic_entry *hde;
+ struct format_field *field;
+ unsigned offset, size;
+
+ hde = container_of(fmt, struct hpp_dynamic_entry, hpp);
+
+ field = hde->field;
+ if (field->flags & FIELD_IS_DYNAMIC) {
+ unsigned long long dyn;
+
+ pevent_read_number_field(field, a->raw_data, &dyn);
+ offset = dyn & 0xffff;
+ size = (dyn >> 16) & 0xffff;
+ } else {
+ offset = field->offset;
+ size = field->size;
+ }
+
+ return memcmp(b->raw_data + offset, a->raw_data + offset, size);
+}
+
bool perf_hpp__is_dynamic_entry(struct perf_hpp_fmt *fmt)
{
return fmt->cmp == __sort__hde_cmp;
@@ -1826,7 +1850,7 @@ __alloc_dynamic_entry(struct perf_evsel *evsel, struct format_field *field)
hde->hpp.cmp = __sort__hde_cmp;
hde->hpp.collapse = __sort__hde_cmp;
- hde->hpp.sort = __sort__hde_cmp;
+ hde->hpp.sort = __sort__hde_sort;
INIT_LIST_HEAD(&hde->hpp.list);
INIT_LIST_HEAD(&hde->hpp.sort_list);
--
2.6.4
next prev parent reply other threads:[~2016-01-07 0:12 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 ` Namhyung Kim [this message]
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
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=1452125549-1511-2-git-send-email-namhyung@kernel.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox