From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Andi Kleen <andi@firstfloor.org>,
Stephane Eranian <eranian@google.com>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH v2 4/8] perf tools: Support multiple sort keys in a hierarchy level
Date: Mon, 7 Mar 2016 21:38:39 +0900 [thread overview]
Message-ID: <20160307123839.GA22896@danjae.kornet> (raw)
In-Reply-To: <20160304214848.GY3604@kernel.org>
Hi Arnaldo,
On Fri, Mar 04, 2016 at 06:48:48PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Mar 04, 2016 at 11:59:38PM +0900, Namhyung Kim escreveu:
> > This implements having multiple sort keys in a single hierarchy level.
>
> > +++ b/tools/perf/util/sort.c
> > @@ -2310,18 +2310,40 @@ static int setup_sort_list(char *str, struct perf_evlist *evlist)
> > char *tmp, *tok;
> > int ret = 0;
> > int level = 0;
> > + int next_level = 1;
> > + bool in_group = false;
> > +
> > + do {
> > + tok = str;
> > + tmp = strpbrk(str, "{}, ");
>
> Ok, I'll test this, but since we use lex/yacc for parsing event
> descriptions, perhaps we should use it here as well? Or do you think
> we're stopping at this level of complexity (I doubt) :-)
I'm not sure how the syntax of sort keys will become more complex.
But I don't think we should use lex/yacc at this level of complexity
Thanks,
Namhyung
>
> > + if (tmp) {
> > + if (in_group)
> > + next_level = level;
> > + else
> > + next_level = level + 1;
> > +
> > + if (*tmp == '{')
> > + in_group = true;
> > + else if (*tmp == '}')
> > + in_group = false;
> > +
> > + *tmp = '\0';
> > + str = tmp + 1;
> > + }
> >
> > - for (tok = strtok_r(str, ", ", &tmp);
> > - tok; tok = strtok_r(NULL, ", ", &tmp)) {
> > - ret = sort_dimension__add(tok, evlist, level++);
> > - if (ret == -EINVAL) {
> > - error("Invalid --sort key: `%s'", tok);
> > - break;
> > - } else if (ret == -ESRCH) {
> > - error("Unknown --sort key: `%s'", tok);
> > - break;
> > + if (*tok) {
> > + ret = sort_dimension__add(tok, evlist, level);
> > + if (ret == -EINVAL) {
> > + error("Invalid --sort key: `%s'", tok);
> > + break;
> > + } else if (ret == -ESRCH) {
> > + error("Unknown --sort key: `%s'", tok);
> > + break;
> > + }
> > }
> > - }
> > +
> > + level = next_level;
> > + } while (tmp);
> >
> > return ret;
> > }
> > --
> > 2.7.2
next prev parent reply other threads:[~2016-03-07 12:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 14:59 [PATCHSET 0/8] perf tools: Support multiple keys in a single hierarchy level (v2) Namhyung Kim
2016-03-04 14:59 ` [PATCH v2 1/8] perf tools: Add level field to struct perf_hpp_fmt Namhyung Kim
2016-03-08 10:32 ` [tip:perf/core] perf hists: " tip-bot for Namhyung Kim
2016-03-04 14:59 ` [PATCH v2 2/8] perf tools: Introduce perf_hpp__setup_hists_formats() Namhyung Kim
2016-03-04 21:58 ` Arnaldo Carvalho de Melo
2016-03-04 21:59 ` Arnaldo Carvalho de Melo
2016-03-07 12:43 ` Namhyung Kim
2016-03-07 13:57 ` Namhyung Kim
2016-03-06 18:43 ` Jiri Olsa
2016-03-07 12:59 ` Namhyung Kim
2016-03-07 13:15 ` Jiri Olsa
2016-03-04 14:59 ` [PATCH v2 3/8] perf tools: Use own hpp_list for hierarchy mode Namhyung Kim
2016-03-05 18:17 ` Jiri Olsa
2016-03-07 12:42 ` Namhyung Kim
2016-03-04 14:59 ` [PATCH v2 4/8] perf tools: Support multiple sort keys in a hierarchy level Namhyung Kim
2016-03-04 21:48 ` Arnaldo Carvalho de Melo
2016-03-07 12:38 ` Namhyung Kim [this message]
2016-03-04 14:59 ` [PATCH v2 5/8] perf tools: Fix indent for multiple hierarchy sort key Namhyung Kim
2016-03-04 14:59 ` [PATCH v2 6/8] perf report: Use hierarchy hpp list on stdio Namhyung Kim
2016-03-04 14:59 ` [PATCH v2 7/8] perf hists browser: Use hierarchy hpp list Namhyung Kim
2016-03-04 14:59 ` [PATCH v2 8/8] perf report: Use hierarchy hpp list on gtk 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=20160307123839.GA22896@danjae.kornet \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®