From: "Falcon, Thomas" <thomas.falcon@intel.com>
To: "alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"acme@kernel.org" <acme@kernel.org>,
"dapeng1.mi@linux.intel.com" <dapeng1.mi@linux.intel.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"irogers@google.com" <irogers@google.com>,
"kan.liang@linux.intel.com" <kan.liang@linux.intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"Mi, Dapeng1" <dapeng1.mi@intel.com>
Subject: Re: [PATCH 1/2] perf x86/topdown: Fix topdown leader sampling test error on hybrid
Date: Tue, 4 Mar 2025 16:49:43 +0000 [thread overview]
Message-ID: <12110f8591ad185e32746b7f8073afda6e99c337.camel@intel.com> (raw)
In-Reply-To: <20250224083306.71813-1-dapeng1.mi@linux.intel.com>
On Mon, 2025-02-24 at 08:33 +0000, Dapeng Mi wrote:
> When running topdown leader smapling test on Intel hybrid platforms,
> such as LNL/ARL, we see the below error.
>
> Topdown leader sampling test
> Topdown leader sampling [Failed topdown events not reordered
> correctly]
>
> It indciates the below command fails.
>
> perf record -o "${perfdata}" -e "{instructions,slots,topdown-
> retiring}:S" true
>
> The root cause is that perf tool creats a perf event for each PMU
> type
> if it can create.
>
> As for this command, there would be 5 perf events created,
> cpu_atom/instructions/,cpu_atom/topdown_retiring/,
> cpu_core/slots/,cpu_core/instructions/,cpu_core/topdown-retiring/
>
> For these 5 events, the 2 cpu_atom events are in a group and the
> other 3
> cpu_core events are in another group.
>
> When arch_topdown_sample_read() traverses all these 5 events, events
> cpu_atom/instructions/ and cpu_core/slots/ don't have a same group
> leade, and then return false directly and lead to cpu_core/slots/
> event
> is used to sample and this is not allowed by PMU driver.
>
> It's a overkill to return false directly if "evsel->core.leader !=
> leader->core.leader" since there could be multiple groups in the
> event
> list.
>
> Just "continue" instead of "return false" to fix this issue.
>
> Fixes: 1e53e9d1787b ("perf x86/topdown: Correct leader selection with
> sample_read enabled")
> Signed-off-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
Tested-by: Thomas Falcon <thomas.falcon@intel.com>
> ---
> tools/perf/arch/x86/util/topdown.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/arch/x86/util/topdown.c
> b/tools/perf/arch/x86/util/topdown.c
> index f63747d0abdf..d1c654839049 100644
> --- a/tools/perf/arch/x86/util/topdown.c
> +++ b/tools/perf/arch/x86/util/topdown.c
> @@ -81,7 +81,7 @@ bool arch_topdown_sample_read(struct evsel *leader)
> */
> evlist__for_each_entry(leader->evlist, evsel) {
> if (evsel->core.leader != leader->core.leader)
> - return false;
> + continue;
> if (evsel != leader &&
> arch_is_topdown_metrics(evsel))
> return true;
> }
>
> base-commit: 4bac7fb5862740087825eda3ed6168e91da8b7e6
next prev parent reply other threads:[~2025-03-04 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 8:33 Dapeng Mi
2025-02-24 8:33 ` [PATCH 2/2] perf tools/tests: Fix topdown groups test on hybrid platforms Dapeng Mi
2025-03-04 16:50 ` Falcon, Thomas
2025-03-05 6:07 ` Ian Rogers
2025-03-05 8:39 ` Ian Rogers
2025-03-04 16:49 ` Falcon, Thomas [this message]
2025-03-05 6:37 ` [PATCH 1/2] perf x86/topdown: Fix topdown leader sampling test error on hybrid Ian Rogers
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=12110f8591ad185e32746b7f8073afda6e99c337.camel@intel.com \
--to=thomas.falcon@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--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 \
/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
all inboxes | Powered by JetHome®