From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>
Cc: acme@kernel.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, jolsa@kernel.org, namhyung@kernel.org,
adrian.hunter@intel.com, tinghao.zhang@intel.com,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] perf evsel: Ignore the non-group case for branch counters
Date: Mon, 13 Nov 2023 11:10:30 -0500 [thread overview]
Message-ID: <d7887fd3-ebf1-47f9-bda7-fd47d79b9807@linux.intel.com> (raw)
In-Reply-To: <CAP-5=fXGavfHvSPs5dRWmS93gspj4uUE6ftd855xFyN-hKRTzg@mail.gmail.com>
On 2023-11-13 10:49 a.m., Ian Rogers wrote:
> On Thu, Nov 9, 2023 at 8:41 AM <kan.liang@linux.intel.com> wrote:
>>
>> From: Kan Liang <kan.liang@linux.intel.com>
>>
>> The perf test 27: Sample parsing fails with the branch counters support
>> introduced.
>>
>> The branch counters feature requires all the events to belong to a
>> group. There is no problem with the normal perf usage which usually
>> initializes an evlist even for a single evsel.
>> But the perf test is special, which may not initialize an evlist. The
>> Sample parsing test case is one of the examples. The existing code
>> crashes with the !evsel->evlist.
>>
>> Non-group means the evsel doesn't have branch counters support.
>
> Thanks Kan, do we need to add this condition to
> parse_events__sort_events_and_fix_groups?
> https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/tree/tools/perf/util/parse-events.c#n2174
>
I don't think so. The "non-group" here means the case that the evlist is
not initialized. It should only happen with some perf test case.
In the parse_events__sort_events_and_fix_groups(), IIUC, the ungrouped
event should mean a single event group. The feature works with the case.
We don't need to add the condition.
BTW: Arnaldo should have already folded it with the original patch. We
don't need the patch anymore.
https://lore.kernel.org/lkml/ZU0pGuUBJH+bF1yU@kernel.org/
Thanks,
Kan
> Ian
>
>> Reported-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>> Closes: https://lore.kernel.org/lkml/ZUv+G+w5EvJgQS45@kernel.org/
>> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
>> ---
>> tools/perf/util/evsel.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
>> index 58a9b8c82790..7a6a2d1f96db 100644
>> --- a/tools/perf/util/evsel.c
>> +++ b/tools/perf/util/evsel.c
>> @@ -2355,6 +2355,10 @@ static inline bool evsel__has_branch_counters(const struct evsel *evsel)
>> {
>> struct evsel *cur, *leader = evsel__leader(evsel);
>>
>> + /* The branch counters feature only supports group */
>> + if (!leader || !evsel->evlist)
>> + return false;
>> +
>> evlist__for_each_entry(evsel->evlist, cur) {
>> if ((leader == evsel__leader(cur)) &&
>> (cur->core.attr.branch_sample_type & PERF_SAMPLE_BRANCH_COUNTERS))
>> --
>> 2.35.1
>>
prev parent reply other threads:[~2023-11-13 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 16:40 [PATCH] perf evsel: Ignore the non-group case for branch counters kan.liang
2023-11-13 15:49 ` Ian Rogers
2023-11-13 16:10 ` Liang, Kan [this message]
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=d7887fd3-ebf1-47f9-bda7-fd47d79b9807@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tinghao.zhang@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