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 1/2] perf evlist: Ensure grouped events with same cpu map
Date: Wed, 27 May 2020 11:20:42 +0800 [thread overview]
Message-ID: <32c4663a-6934-2a2d-79e2-7a335e3629a2@linux.intel.com> (raw)
In-Reply-To: <20200526115155.GE333164@krava>
Hi Jiri,
On 5/26/2020 7:51 PM, Jiri Olsa wrote:
> On Mon, May 25, 2020 at 02:55:58PM +0800, Jin Yao wrote:
>
> SNIP
>
>> diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
>> index 2a9de6491700..1161cffc0688 100644
>> --- a/tools/perf/util/evlist.c
>> +++ b/tools/perf/util/evlist.c
>> @@ -1704,3 +1704,52 @@ struct evsel *perf_evlist__reset_weak_group(struct evlist *evsel_list,
>> }
>> return leader;
>> }
>> +
>> +static bool cpus_map_matched(struct evsel *prev, struct evsel *evsel)
>> +{
>> + if (evsel->core.cpus->nr != prev->core.cpus->nr)
>> + return false;
>> +
>> + for (int i = 0; i < evsel->core.cpus->nr; i++) {
>> + if (evsel->core.cpus->map[i] != prev->core.cpus->map[i])
>> + return false;
>> + }
>> +
>> + return true;
>> +}
>> +
>> +bool evlist__cpus_map_matched(struct evlist *evlist)
>> +{
>> + struct evsel *prev = evlist__first(evlist), *evsel = prev;
>> + int nr_members = prev->core.nr_members;
>> +
>> + evlist__for_each_entry_continue(evlist, evsel) {
>> + if (nr_members <= 1) {
>> + prev = evsel;
>> + nr_members = evsel->core.nr_members;
>> + continue;
>> + }
>> +
>> + nr_members--;
>> +
>> + if (!cpus_map_matched(prev, evsel))
>> + return false;
>> +
>> + prev = evsel;
>> + }
>> +
>> + return true;
>> +}
>> +
>> +void evlist__force_disable_group(struct evlist *evlist)
>> +{
>> + struct evsel *evsel;
>> +
>> + pr_warning("WARNING: event cpu maps are not fully matched, "
>> + "stop event grouping\n");
>> +
>> + evlist__for_each_entry(evlist, evsel) {
>> + evsel->leader = evsel;
>> + evsel->core.nr_members = 0;
>> + }
>> +}
>
> I think this is too much, we need to disable only groups with not
> matching cpus, not all of them, how about something like this
>
Yes, that's too much.
>
> struct evsel *pos;
>
> evlist__for_each_entry(evlist, evsel) {
> if (evsel->leader == evsel)
> continue;
> if (!cpus_map_matched(evsel->leader, evsel))
> continue;
>
> pr_warn("Disabling group...
>
> for_each_group_member(pos, evsel->leader) {
> pos->leader = pos;
> evsel->core.nr_members = 0;
> }
> }
>
> jirka
>
Hmm, change "!cpus_map_matched()" to "cpus_map_matched()"? and use for_each_group_evsel() to replace
for_each_group_member()?
How about something like following?
void evlist__check_cpu_maps(struct evlist *evlist)
{
struct evsel *evsel, *pos;
evlist__for_each_entry(evlist, evsel) {
if (evsel->leader == evsel)
continue;
if (cpu_maps_matched(evsel->leader, evsel))
continue;
pr_warning("WARNING: event cpu maps are not fully matched, "
"disable group\n");
for_each_group_evsel(pos, evsel->leader) {
pos->leader = pos;
pos->core.nr_members = 0;
}
/*
* For core & uncore mixed event group, for example,
* '{cycles,unc_cbo_cache_lookup.any_i}',
* In evlist:
* cycles,
* unc_cbo_cache_lookup.any_i,
* unc_cbo_cache_lookup.any_i,
* unc_cbo_cache_lookup.any_i,
* unc_cbo_cache_lookup.any_i,
*
* cycles is leader and all unc_cbo_cache_lookup.any_i
* point to this leader. But for_each_group_evsel can't
* iterate all members from cycles. It only iterates
* cycles and one unc_cbo_cache_lookup.any_i. So we
* set extra evsel here.
*/
evsel->leader = evsel;
evsel->core.nr_members = 0;
}
}
Thanks
Jin Yao
next prev parent reply other threads:[~2020-05-27 3:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 6:55 [PATCH v2 1/2] perf evlist: Ensure grouped events with same cpu map Jin Yao
2020-05-25 6:55 ` [PATCH v2 2/2] perf test: Add test case for group members Jin Yao
2020-05-26 11:51 ` [PATCH v2 1/2] perf evlist: Ensure grouped events with same cpu map Jiri Olsa
2020-05-27 3:20 ` Jin, Yao [this message]
2020-05-27 6:31 ` Jin, Yao
2020-05-27 7:26 ` Jin, Yao
2020-05-27 10:28 ` Jiri Olsa
2020-05-27 13:49 ` Jin, Yao
2020-05-27 16:28 ` Jiri Olsa
2020-05-28 1:47 ` 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=32c4663a-6934-2a2d-79e2-7a335e3629a2@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