From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v4 1/2] perf tests: Add test for uncore event sorting
Date: Sun, 17 May 2026 23:49:13 +0000 [thread overview]
Message-ID: <20260517234913.D82BFC2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260517232849.2391357-2-irogers@google.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The test fails to verify that events from multiple PMUs were actually parsed, allowing it to silently pass without exercising the multi-PMU sorting logic.
--
commit 7547d1b7750e7305c495d31d775f2a8e3af0325a
Author: Ian Rogers <irogers@google.com>
perf tests: Add test for uncore event sorting
This commit adds a test to verify that uncore events with a common PMU prefix
are properly resorted when parsed. It sets up a scenario matching multiple
sibling PMUs and checks that the resulting event list correctly groups the
events by PMU.
> diff --git a/tools/perf/tests/uncore-event-sorting.c b/tools/perf/tests/uncore-event-sorting.c
> new file mode 100644
> --- /dev/null
> +++ b/tools/perf/tests/uncore-event-sorting.c
[ ... ]
> + parse_events_error__init(&err);
> + ret = parse_events(evlist, buf, &err);
> + if (ret) {
> + pr_debug("parse_events failed\n");
> + ret = TEST_FAIL;
> + goto out_err;
> + }
> +
> + TEST_ASSERT_VAL("Number of events is > 0", evlist->core.nr_entries > 0);
> + TEST_ASSERT_EQUAL("Number of events is a multiple of 2", evlist->core.nr_entries % 2, 0);
If parse_events() encounters a regression and only matches a single PMU instead
of expanding to all siblings, evlist->core.nr_entries would evaluate to 2.
Since 2 is greater than 0 and a multiple of 2, wouldn't the test silently pass
without actually exercising the multi-PMU sorting logic it was designed for?
Should this test assert that evlist->core.nr_entries >= 4 to guarantee that
the mixed PMU resorting scenario is genuinely validated?
> +
> + evlist__for_each_entry(evlist, evsel) {
> + struct evsel *next;
> +
> + if (!evsel__is_group_leader(evsel))
> + continue;
> +
> + next = evsel__next(evsel);
> + TEST_ASSERT_EQUAL("Group size is 2", evsel->core.nr_members, 2);
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260517232849.2391357-1-irogers@google.com?part=1
next prev parent reply other threads:[~2026-05-17 23:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 18:30 [PATCH v1 0/2] perf tests: Add tests for uncore and perf metric event sorting Ian Rogers
2026-03-25 18:30 ` [PATCH v1 1/2] perf tests: Add test for uncore " Ian Rogers
2026-03-27 23:36 ` Chen, Zide
2026-03-31 3:06 ` Namhyung Kim
2026-03-25 18:30 ` [PATCH v1 2/2] perf arch x86 tests: Add test for topdown " Ian Rogers
2026-03-30 21:53 ` Chen, Zide
2026-03-31 3:08 ` Namhyung Kim
2026-03-31 16:52 ` [PATCH v2 0/2] perf tests: Add tests for uncore and perf metric " Ian Rogers
2026-03-31 16:52 ` [PATCH v2 1/2] perf tests: Add test for uncore " Ian Rogers
2026-03-31 16:52 ` [PATCH v2 2/2] perf arch x86 tests: Add test for topdown " Ian Rogers
2026-03-31 18:54 ` [PATCH v3 0/2] Add tests for uncore and perf metric " Ian Rogers
2026-03-31 18:54 ` [PATCH v3 1/2] perf tests: Add test for uncore " Ian Rogers
2026-04-01 21:48 ` Namhyung Kim
2026-03-31 18:54 ` [PATCH v3 2/2] perf arch x86 tests: Add test for topdown " Ian Rogers
2026-04-01 3:33 ` Namhyung Kim
2026-05-17 23:28 ` [PATCH v4 0/2] perf tests: Add uncore and x86 topdown event sorting tests Ian Rogers
2026-05-17 23:28 ` [PATCH v4 1/2] perf tests: Add test for uncore event sorting Ian Rogers
2026-05-17 23:49 ` sashiko-bot [this message]
2026-05-17 23:28 ` [PATCH v4 2/2] perf arch x86 tests: Add test for topdown " Ian Rogers
2026-05-18 0:05 ` sashiko-bot
2026-05-18 0:37 ` [PATCH v5 0/2] perf tests: Add uncore and x86 topdown event sorting tests Ian Rogers
2026-05-18 0:37 ` [PATCH v5 1/2] perf tests: Add test for uncore event sorting Ian Rogers
2026-05-18 1:06 ` sashiko-bot
2026-05-18 0:37 ` [PATCH v5 2/2] perf arch x86 tests: Add test for topdown " Ian Rogers
2026-05-18 1:20 ` sashiko-bot
2026-05-18 2:32 ` [PATCH v6 0/2] perf tests: Add uncore and x86 topdown event sorting tests Ian Rogers
2026-05-18 2:32 ` [PATCH v6 1/2] perf tests: Add test for uncore event sorting Ian Rogers
2026-05-18 2:53 ` sashiko-bot
2026-05-18 2:32 ` [PATCH v6 2/2] perf arch x86 tests: Add test for topdown " Ian Rogers
2026-05-18 3:08 ` sashiko-bot
2026-05-18 4:31 ` [PATCH v7 0/2] perf tests: Add uncore and x86 topdown event sorting tests Ian Rogers
2026-05-18 4:31 ` [PATCH v7 1/2] perf tests: Add test for uncore event sorting Ian Rogers
2026-05-18 4:48 ` sashiko-bot
2026-05-18 4:31 ` [PATCH v7 2/2] perf arch x86 tests: Add test for topdown " Ian Rogers
2026-05-18 6:29 ` [PATCH v8 0/2] perf tests: Add uncore and x86 topdown event sorting tests Ian Rogers
2026-05-18 6:29 ` [PATCH v8 1/2] perf tests: Add test for uncore event sorting Ian Rogers
2026-05-18 6:29 ` [PATCH v8 2/2] perf arch x86 tests: Add test for topdown " Ian Rogers
2026-05-20 15:31 ` [PATCH v8 0/2] perf tests: Add uncore and x86 topdown event sorting tests Ian Rogers
2026-05-20 20:28 ` Namhyung Kim
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=20260517234913.D82BFC2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.