From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Rob Herring <robh@kernel.org>,
Ravi Bangoria <ravi.bangoria@amd.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Richter <tmricht@linux.ibm.com>
Subject: Re: [PATCH v2 1/4] perf pmu: Correct perf_pmu__auto_merge_stats affecting hybrid
Date: Thu, 1 Jun 2023 09:52:06 -0400 [thread overview]
Message-ID: <7b23aee2-9fec-e07c-4ca1-076a061c558b@linux.intel.com> (raw)
In-Reply-To: <20230601082954.754318-2-irogers@google.com>
On 2023-06-01 4:29 a.m., Ian Rogers wrote:
> Flip the return value correcting a bug.
The bug is that perf fails to create a normal core event on each hybrid
PMU even if the event is available on all hybrid PMUs.
Without the patch,
# ./perf_old stat -e inst_retired.any -a sleep 1
Performance counter stats for 'system wide':
21,760,495 cpu_core/inst_retired.any/
1.004010591 seconds time elapsed
With the patch,
# ./perf stat -e inst_retired.any -a sleep 1
Performance counter stats for 'system wide':
19,874,833 cpu_core/inst_retired.any/
3,102,256 cpu_atom/inst_retired.any/
1.004081307 seconds time elapsed
I think we need to fold the above to the description.
Thanks,
Kan
>
> Fixes: 6b9da2607030 ("perf pmu: Remove is_pmu_hybrid")
> Reported-by: Kan Liang <kan.liang@linux.intel.com>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/util/pmu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
> index 0520aa9fe991..36e163f38368 100644
> --- a/tools/perf/util/pmu.c
> +++ b/tools/perf/util/pmu.c
> @@ -1424,7 +1424,7 @@ bool perf_pmu__supports_legacy_cache(const struct perf_pmu *pmu)
>
> bool perf_pmu__auto_merge_stats(const struct perf_pmu *pmu)
> {
> - return pmu->is_core && perf_pmus__num_core_pmus() > 1;
> + return pmu->is_core && perf_pmus__num_core_pmus() == 1;
> }
>
> bool perf_pmu__have_event(const struct perf_pmu *pmu, const char *name)
next prev parent reply other threads:[~2023-06-01 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 8:29 [PATCH v2 0/4] Hybrid event parsing fixes Ian Rogers
2023-06-01 8:29 ` [PATCH v2 1/4] perf pmu: Correct perf_pmu__auto_merge_stats affecting hybrid Ian Rogers
2023-06-01 13:52 ` Liang, Kan [this message]
2023-06-01 8:29 ` [PATCH v2 2/4] perf evsel: Add verbose 3 print of evsel name when opening Ian Rogers
2023-06-01 8:29 ` [PATCH v2 3/4] perf parse-events: Wildcard most "numeric" events Ian Rogers
2023-06-01 13:52 ` Liang, Kan
2023-06-01 8:29 ` [PATCH v2 4/4] perf test: Update parse-events expectations Ian Rogers
2023-06-01 13:59 ` [PATCH v2 0/4] Hybrid event parsing fixes Liang, Kan
2023-06-01 17:39 ` Arnaldo Carvalho de Melo
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=7b23aee2-9fec-e07c-4ca1-076a061c558b@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=robh@kernel.org \
--cc=tmricht@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).