From: Jiri Olsa <jolsa@redhat.com>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: kernel test robot <oliver.sang@intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Matthew Brost <matthew.brost@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com, Andi Kleen <ak@linux.intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@intel.com>,
"Jin, Yao" <yao.jin@intel.com>, "Yi, Ammy" <ammy.yi@intel.com>
Subject: Re: [drm/i915/gt] 8c3b1ba0e7: perf-sanity-tests.Parse_event_definition_strings.fail
Date: Thu, 25 Feb 2021 20:03:24 +0100 [thread overview]
Message-ID: <YDf0fP8XmnTrkIT8@krava> (raw)
In-Reply-To: <YDfxgfi5DBDMFgwu@krava>
On Thu, Feb 25, 2021 at 07:50:46PM +0100, Jiri Olsa wrote:
> On Thu, Feb 25, 2021 at 07:16:44PM +0100, Jiri Olsa wrote:
> > On Thu, Feb 25, 2021 at 02:33:57PM +0100, Jiri Olsa wrote:
> > > On Thu, Feb 25, 2021 at 04:06:23PM +0800, Jin, Yao wrote:
> > > > Hi Chris, Arnaldo, Jiri,
> > > >
> > > > We observe the parsing error for "software/xxx/" on some platforms.
> > > >
> > > > For example,
> > > >
> > > > # perf stat -e software/r1a/ -a -- sleep 1
> > > > event syntax error: 'software/r1a/'
> > > > \___ parser error
> > > > Run 'perf list' for a list of valid events
> > > >
> > > > Usage: perf stat [<options>] [<command>]
> > > >
> > > > -e, --event <event> event selector. use 'perf list' to list available events
> > > >
> > > > And perf test is failed too.
> > > >
> > > > # perf test 6 -vv
> > > > ...
> > > > running test 4 'software/r1a/'failed to parse event 'software/r1a/', err 1, str 'parser error'
> > > > event syntax error: 'software/r1a/'
> > > > \___ parser error
> > > >
> > > > running test 4 'software/r0x1a/'failed to parse event 'software/r0x1a/', err 1, str 'parser error'
> > > > event syntax error: 'software/r0x1a/'
> > > > \___ parser error
> > > > ...
> > > >
> > > > The issue should be the conflict between event "i915/software-gt-awake-time/" and pmu "software".
> > > >
> > > > # perf list | grep i915/software
> > > > i915/software-gt-awake-time/ [Kernel PMU event]
> > > >
> > > > Perf supports the event format as "prefix-xxx-suffix", so the "software"
> > > > string in "software-gt-awake-time" is added to perf_pmu_events_list as
> > > > PMU_EVENT_SYMBOL_PREFIX. When parsing the string such as "software/xxx/",
> > > > it’s parsed as PMU_EVENT_SYMBOL_PREFIX for "software", then it would error
> > > > out in next processing.
> > > >
> > > > So the easy way is to rename "software-gt-awake-time" to "gt-awake-time",
> > > > right? Otherwise we have to hardcode something in perf tool.
> > > >
> > > > What do you think of this issue and the solution?
> > > >
> > > > BTW, as the robot reported, it's related to the commit 8c3b1ba0e7ea
> > > > ("drm/i915/gt: Track the overall awake/busy time").
> > >
> > > yes, I think you're right.. I'll try to reproduce and check on this
> > >
> > > I'm still not clear why is that parsing fail if those 2 events are
> > > distinguished by - and / ... but yep, we are asking for trouble in
> > > here ;-)
> > >
> > > I think we could either prioritaze one or add extra check when we
> > > add prefix-xxx-suffix events and do not add ones that have conflict..
> > > that seems like best solution to me now
> >
> > would patch below work for you?
> >
> > jirka
>
> and now with more fixes after I ran tests ;-)
>
> we should perhaps add also same check for non '-' aliases, I'll check
and one more version ;-)
jirka
---
diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
index 42c84adeb2fb..d9e795056d15 100644
--- a/tools/perf/util/parse-events.c
+++ b/tools/perf/util/parse-events.c
@@ -2028,30 +2028,49 @@ static void perf_pmu__parse_init(void)
perf_pmu_events_list_num = -1;
return;
}
- perf_pmu_events_list = malloc(sizeof(struct perf_pmu_event_symbol) * len);
+ perf_pmu_events_list = zalloc(sizeof(struct perf_pmu_event_symbol) * len);
if (!perf_pmu_events_list)
return;
- perf_pmu_events_list_num = len;
len = 0;
pmu = NULL;
while ((pmu = perf_pmu__scan(pmu)) != NULL) {
list_for_each_entry(alias, &pmu->aliases, list) {
struct perf_pmu_event_symbol *p = perf_pmu_events_list + len;
- char *tmp = strchr(alias->name, '-');
+ char *prefix = strdup(alias->name);
+ char *tmp = strchr(prefix, '-');
+
+ if (tmp != NULL)
+ *tmp = 0;
+
+ /*
+ * Skip any prefix that conflicts with pmu name,
+ * otherwise the event parser gets confused.
+ */
+ if (perf_pmu__find(prefix)) {
+ pr_debug2("perf_pmu__parse_init: skipping conflicting alias '%s'\n",
+ alias->name);
+ free(prefix);
+ continue;
+ }
if (tmp != NULL) {
- SET_SYMBOL(strndup(alias->name, tmp - alias->name),
- PMU_EVENT_SYMBOL_PREFIX);
+ SET_SYMBOL(prefix, PMU_EVENT_SYMBOL_PREFIX);
p++;
SET_SYMBOL(strdup(++tmp), PMU_EVENT_SYMBOL_SUFFIX);
len += 2;
} else {
- SET_SYMBOL(strdup(alias->name), PMU_EVENT_SYMBOL);
+ SET_SYMBOL(prefix, PMU_EVENT_SYMBOL);
len++;
}
}
}
+
+ /* unlikely, but still.. */
+ if (!len)
+ goto err;
+ perf_pmu_events_list_num = len;
+
qsort(perf_pmu_events_list, len,
sizeof(struct perf_pmu_event_symbol), comp_pmu);
next prev parent reply other threads:[~2021-02-25 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 7:48 [drm/i915/gt] 8c3b1ba0e7: perf-sanity-tests.Parse_event_definition_strings.fail kernel test robot
2021-02-25 8:06 ` Jin, Yao
2021-02-25 13:33 ` Jiri Olsa
2021-02-25 18:16 ` Jiri Olsa
2021-02-25 18:50 ` Jiri Olsa
2021-02-25 19:03 ` Jiri Olsa [this message]
2021-02-26 0:41 ` Jin, Yao
2021-02-27 10:21 ` Jiri Olsa
2021-02-28 9:33 ` Jiri Olsa
2021-03-01 1:12 ` Jin, Yao
-- strict thread matches above, loose matches on Subject: below --
2020-12-26 10:58 kernel test robot
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=YDf0fP8XmnTrkIT8@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=ammy.yi@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=matthew.brost@intel.com \
--cc=oliver.sang@intel.com \
--cc=tvrtko.ursulin@intel.com \
--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