mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 2/2] perf tools/tests: Fix topdown groups test on hybrid platforms
Date: Tue, 4 Mar 2025 16:50:00 +0000	[thread overview]
Message-ID: <b9a0773abd2ee44ba1d91596a82633fe999f35c4.camel@intel.com> (raw)
In-Reply-To: <20250224083306.71813-2-dapeng1.mi@linux.intel.com>

On Mon, 2025-02-24 at 08:33 +0000, Dapeng Mi wrote:
> When running topdown groups test on hybrid platforms like LNL/ARL, we
> see the following 2 commands fail.
> 
> perf stat $cputype -e '{instructions,slots},topdown-retiring' true
> perf stat $cputype -e '{instructions,slots},{topdown-retiring}' true
> 
> Take the 1st command as an example, 5 events are created on hybrid
> platform. They are cpu_atom/instructions/, cpu_core/instructions/,
> cpu_core/slots/, cpu_atom/topdown-retiring/ and
> cpu_core/topdown-retiring/ events. The former 3 events are in a group
> and the latter 2 topdown-retiring events are independent events.
> 
> As the limitation of current implementation, the
> cpu_core/topdown-retiring/ event can't be moved into previous group
> as
> long as there are other events before it. That's the reason why we
> see
> the failure.
> 
> Thus add "--cputype core" option to limit only P-core events are
> tested.
> 
> Signed-off-by: Dapeng Mi <dapeng1.mi@linux.intel.com>

Tested-by: Thomas Falcon <thomas.falcon@intel.com>

> ---
>  tools/perf/arch/x86/util/evlist.c | 26 +++++++++++++++++++++++---
>  tools/perf/tests/shell/stat.sh    | 20 ++++++++++++++++++--
>  2 files changed, 41 insertions(+), 5 deletions(-)
> 
> diff --git a/tools/perf/arch/x86/util/evlist.c
> b/tools/perf/arch/x86/util/evlist.c
> index 447a734e591c..0a71ba975871 100644
> --- a/tools/perf/arch/x86/util/evlist.c
> +++ b/tools/perf/arch/x86/util/evlist.c
> @@ -9,7 +9,7 @@ int arch_evlist__cmp(const struct evsel *lhs, const
> struct evsel *rhs)
>  {
>  	/*
>  	 * Currently the following topdown events sequence are
> supported to
> -	 * move and regroup correctly.
> +	 * move and regroup correctly on non-hybrid platforms.
>  	 *
>  	 * a. all events in a group
>  	 *    perf stat -e "{instructions,topdown-retiring,slots}" -
> C0 sleep 1
> @@ -44,7 +44,7 @@ int arch_evlist__cmp(const struct evsel *lhs, const
> struct evsel *rhs)
>  	 * topdown metrics events must be first event after the
> slots event group,
>  	 * otherwise topdown metrics events can't be regrouped
> correctly, e.g.
>  	 *
> -	 * a. perf stat -e "{instructions,slots},cycles,topdown-
> retiring" -C0 sleep 1
> +	 * e. perf stat -e "{instructions,slots},cycles,topdown-
> retiring" -C0 sleep 1
>  	 *    WARNING: events were regrouped to match PMUs
>  	 *     Performance counter stats for 'CPU(s) 0':
>  	 *         17,923,134      slots
> @@ -56,11 +56,31 @@ int arch_evlist__cmp(const struct evsel *lhs,
> const struct evsel *rhs)
>  	 * has topdown metrics events must contain only the topdown
> metrics event,
>  	 * otherwise topdown metrics event can't be regrouped
> correctly as well, e.g.
>  	 *
> -	 * a. perf stat -e "{instructions,slots},{topdown-
> retiring,cycles}" -C0 sleep 1
> +	 * f. perf stat -e "{instructions,slots},{topdown-
> retiring,cycles}" -C0 sleep 1
>  	 *    WARNING: events were regrouped to match PMUs
>  	 *    Error:
>  	 *    The sys_perf_event_open() syscall returned with 22
> (Invalid argument) for
>  	 *    event (topdown-retiring)
> +	 *
> +	 * For hybrid platforms, the sequences 'c' and 'd' are not
> supported as well
> +	 * besides above sequences 'e' and 'f'.
> +	 *
> +	 *    perf stat -e "{instructions,slots},topdown-retiring" -
> C0 sleep 1
> +	 *    perf stat -e "{instructions,slots},{topdown-retiring}"
> -C0 sleep 1
> +	 *
> +	 * On hybrid platforms each event would create an instance
> on all types of PMU
> +	 * if the event can be supported by the PMU, i.e., the
> "topdown-retiring" event
> +	 * would create two instances on hybrid platforms with P-
> cores and E-cores,
> +	 * "cpu_core/topdown-retiring/" and
> "cpu_atom/topdown_retiring".
> +	 *
> +	 * Take the first command as an example, the events list
> would be converted to
> +	 * below list in fact.
> +	 *
> +	 *
> "{cpu_atom/instructions/,cpu_core/instructions/,cpu_core/slots/},
> +	 *  cpu_atom/topdown-retiring/,cpu_core/topdown-retiring/"
> +	 *
> +	 * This is actually same with event list in case 'e',
> "cpu_core/topdown-retiring/"
> +	 * event can't be moved into previous events group.
>  	 */
>  	if (topdown_sys_has_perf_metrics() &&
>  	    (arch_evsel__must_be_in_group(lhs) ||
> arch_evsel__must_be_in_group(rhs))) {
> diff --git a/tools/perf/tests/shell/stat.sh
> b/tools/perf/tests/shell/stat.sh
> index 68323d636fb7..cdfe27c25528 100755
> --- a/tools/perf/tests/shell/stat.sh
> +++ b/tools/perf/tests/shell/stat.sh
> @@ -5,6 +5,16 @@
>  set -e
>  
>  err=0
> +is_hybrid=false
> +
> +check_hybrid_platform() {
> +  pmus=$(ls /sys/bus/event_source/devices/*/cpus 2>/dev/null | wc -
> l)
> +  if [ "$pmus" -gt 1 ]
> +  then
> +    is_hybrid=true
> +  fi
> +}
> +
>  test_default_stat() {
>    echo "Basic stat command test"
>    if ! perf stat true 2>&1 | grep -E -q "Performance counter stats
> for 'true':"
> @@ -62,6 +72,11 @@ test_topdown_groups() {
>    # Topdown events must be grouped with the slots event first. Test
> that
>    # parse-events reorders this.
>    echo "Topdown event group test"
> +  cputype=""
> +  if $is_hybrid
> +  then
> +    cputype="--cputype core"
> +  fi
>    if ! perf stat -e '{slots,topdown-retiring}' true > /dev/null 2>&1
>    then
>      echo "Topdown event group test [Skipped event parsing failed]"
> @@ -85,13 +100,13 @@ test_topdown_groups() {
>      err=1
>      return
>    fi
> -  if perf stat -e '{instructions,slots},topdown-retiring' true 2>&1
> | grep -E -q "<not supported>"
> +  if perf stat $cputype -e '{instructions,slots},topdown-retiring'
> true 2>&1 | grep -E -q "<not supported>"
>    then
>      echo "Topdown event group test [Failed topdown metrics event not
> move into slots group]"
>      err=1
>      return
>    fi
> -  if perf stat -e '{instructions,slots},{topdown-retiring}' true
> 2>&1 | grep -E -q "<not supported>"
> +  if perf stat $cputype -e '{instructions,slots},{topdown-retiring}'
> true 2>&1 | grep -E -q "<not supported>"
>    then
>      echo "Topdown event group test [Failed topdown metrics group not
> merge into slots group]"
>      err=1
> @@ -200,6 +215,7 @@ test_hybrid() {
>    echo "hybrid test [Success]"
>  }
>  
> +check_hybrid_platform
>  test_default_stat
>  test_stat_record_report
>  test_stat_record_script


  reply	other threads:[~2025-03-04 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24  8:33 [PATCH 1/2] perf x86/topdown: Fix topdown leader sampling test error on hybrid 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 [this message]
2025-03-05  6:07   ` Ian Rogers
2025-03-05  8:39     ` Ian Rogers
2025-03-04 16:49 ` [PATCH 1/2] perf x86/topdown: Fix topdown leader sampling test error on hybrid Falcon, Thomas
2025-03-05  6:37   ` 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=b9a0773abd2ee44ba1d91596a82633fe999f35c4.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®