From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v3 1/3] perf evlist: Create a new function perf_evlist_forced_leader
Date: Fri, 18 May 2018 11:18:58 -0300 [thread overview]
Message-ID: <20180518141858.GC32141@kernel.org> (raw)
In-Reply-To: <1526659234-1556-2-git-send-email-yao.jin@linux.intel.com>
Em Sat, May 19, 2018 at 12:00:32AM +0800, Jin Yao escreveu:
> For non-explicit group, perf report supports a option '--group'
> which can enable group output. We also need to support perf annotate
> with the same '--group'.
>
> Create a new function perf_evlist_forced_leader which contains
> common code to force setting the group leader.
>
> Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
> ---
> tools/perf/util/evlist.c | 15 +++++++++++++++
> tools/perf/util/evlist.h | 3 +++
> 2 files changed, 18 insertions(+)
>
> diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
> index a59281d..6983f6a 100644
> --- a/tools/perf/util/evlist.c
> +++ b/tools/perf/util/evlist.c
> @@ -1795,3 +1795,18 @@ bool perf_evlist__exclude_kernel(struct perf_evlist *evlist)
>
> return true;
> }
> +
> +/*
> + * Events in data file are not collect in groups, but we still want
> + * the group display. Set the artificial group and set the leader's
> + * forced_leader flag to notify the display code.
> + */
> +void perf_evlist_forced_leader(struct perf_evlist *evlist)
This should've been:
void perf_evlist__forced_leader(struct perf_evlist *evlist)
But then, by the verb conjugation, I thought that this would be a query,
i.e. "is this a forced leader?", but then, it returning void didn't
match that expectation, which leads me having to actually _read_ that
code to understand what is that this function does, which I would, but
just to check that it matches what it seems to be, now I'm trying to do
it to figure it out what is it that this thing does :-\
I see, its a 'd' to many, this should be:
void perf_evlist__force_leader(struct perf_evlist *evlist)
Please confirm that this is what you intend by posting a v4, so far,
just for this specific patch and any other in the series that uses this
function, ok?
- Arnaldo
> +{
> + if (!evlist->nr_groups) {
> + struct perf_evsel *leader = perf_evlist__first(evlist);
> +
> + perf_evlist__set_leader(evlist);
> + leader->forced_leader = true;
> + }
> +}
> diff --git a/tools/perf/util/evlist.h b/tools/perf/util/evlist.h
> index 6c41b2f..d77d514 100644
> --- a/tools/perf/util/evlist.h
> +++ b/tools/perf/util/evlist.h
> @@ -309,4 +309,7 @@ struct perf_evsel *perf_evlist__event2evsel(struct perf_evlist *evlist,
> union perf_event *event);
>
> bool perf_evlist__exclude_kernel(struct perf_evlist *evlist);
> +
> +void perf_evlist_forced_leader(struct perf_evlist *evlist);
> +
> #endif /* __PERF_EVLIST_H */
> --
> 2.7.4
next prev parent reply other threads:[~2018-05-18 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 16:00 [PATCH v3 0/3] perf annotate: Support '--group' option Jin Yao
2018-05-18 16:00 ` [PATCH v3 1/3] perf evlist: Create a new function perf_evlist_forced_leader Jin Yao
2018-05-18 14:18 ` Arnaldo Carvalho de Melo [this message]
2018-05-18 21:30 ` Jin, Yao
2018-05-18 16:00 ` [PATCH v3 2/3] perf report: Use perf_evlist_forced_leader to support '--group' Jin Yao
2018-05-18 16:00 ` [PATCH v3 3/3] perf annotate: Support '--group' option Jin Yao
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=20180518141858.GC32141@kernel.org \
--to=acme@kernel.org \
--cc=Linux-kernel@vger.kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
--cc=yao.jin@linux.intel.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