From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@kernel.org, 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 v2 2/3] perf report: Use perf_evlist_forced_leader to support '--group'
Date: Fri, 18 May 2018 15:21:53 +0800 [thread overview]
Message-ID: <2079e88e-7c15-9589-3ce8-9fe831bf60f1@linux.intel.com> (raw)
In-Reply-To: <20180518070441.GB30793@krava>
On 5/18/2018 3:04 PM, Jiri Olsa wrote:
> On Fri, May 18, 2018 at 08:57:39PM +0800, Jin Yao wrote:
>> Since we have created a new function perf_evlist_forced_leader,
>> so now remove the old code and use perf_evlist_forced_leader
>> instead.
>>
>> Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
>> ---
>> tools/perf/builtin-report.c | 8 ++------
>> 1 file changed, 2 insertions(+), 6 deletions(-)
>>
>> diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
>> index 4c931af..63fe776 100644
>> --- a/tools/perf/builtin-report.c
>> +++ b/tools/perf/builtin-report.c
>> @@ -202,12 +202,8 @@ static int hist_iter__branch_callback(struct hist_entry_iter *iter,
>
> there's comment in this place, which no longer applies in here:
>
>
> /*
> * 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.
> */
>
> could you please move/change/apply it to perf_evlist_forced_leader
>
> thanks,
> jirka
>
Oh, yes, I should move the comment to perf_evlist_forced_leader.
I will do it in next version.
Thanks
Jin Yao
>> static void setup_forced_leader(struct report *report,
>> struct perf_evlist *evlist)
>
>> {
>> - if (report->group_set && !evlist->nr_groups) {
>> - struct perf_evsel *leader = perf_evlist__first(evlist);
>> -
>> - perf_evlist__set_leader(evlist);
>> - leader->forced_leader = true;
>> - }
>> + if (report->group_set)
>> + perf_evlist_forced_leader(evlist);
>> }
>>
>> static int process_feature_event(struct perf_tool *tool,
>> --
>> 2.7.4
>>
next prev parent reply other threads:[~2018-05-18 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 12:57 [PATCH v2 0/3] perf annotate: Support '--group' option Jin Yao
2018-05-18 12:57 ` [PATCH v2 1/3] perf evlist: Create a new function perf_evlist_forced_leader Jin Yao
2018-05-18 12:57 ` [PATCH v2 2/3] perf report: Use perf_evlist_forced_leader to support '--group' Jin Yao
2018-05-18 7:04 ` Jiri Olsa
2018-05-18 7:21 ` Jin, Yao [this message]
2018-05-18 12:57 ` [PATCH v2 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=2079e88e-7c15-9589-3ce8-9fe831bf60f1@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@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