From: Ingo Molnar <mingo@kernel.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com, tglx@linutronix.de,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, gautham.shenoy@amd.com, ravi.bangoria@amd.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] perf/x86/rapl: Fix the energy-pkg event for AMD CPUs
Date: Thu, 5 Sep 2024 12:07:46 +0200 [thread overview]
Message-ID: <ZtmC8hhpUvQTXFDn@gmail.com> (raw)
In-Reply-To: <90028792-19b0-4371-a8b4-0a37612b4c9b@linux.intel.com>
* Liang, Kan <kan.liang@linux.intel.com> wrote:
>
>
> On 2024-09-04 6:09 a.m., Dhananjay Ugwekar wrote:
> > After commit ("x86/cpu/topology: Add support for the AMD 0x80000026 leaf"),
> > on AMD processors that support extended CPUID leaf 0x80000026, the
> > topology_die_cpumask() and topology_logical_die_id() macros, no longer
> > return the package cpumask and package id, instead they return the CCD
> > (Core Complex Die) mask and id respectively. This leads to the energy-pkg
> > event scope to be modified to CCD instead of package.
> >
> > So, change the PMU scope for AMD and Hygon back to package.
> >
> > On a 12 CCD 1 Package AMD Zen4 Genoa machine:
> >
> > Before:
> > $ cat /sys/devices/power/cpumask
> > 0,8,16,24,32,40,48,56,64,72,80,88.
> >
> > The expected cpumask here is supposed to be just "0", as it is a package
> > scope event, only one CPU will be collecting the event for all the CPUs in
> > the package.
> >
> > After:
> > $ cat /sys/devices/power/cpumask
> > 0
> >
> > Signed-off-by: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
>
> Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
Note that I just merged the older v2 version into perf/urgent, because it's
a regression fix, and to not create a backporting complication. I added
your Reviewed-by to it if that's fine with you.
Your hotplug series can essentially revert this:
8d72eba1cf8c ("perf/x86/rapl: Fix the energy-pkg event for AMD CPUs")
and apply the v3 patch to gain the simpler version.
Thanks,
Ingo
next prev parent reply other threads:[~2024-09-05 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 10:09 [PATCH v3] perf/x86/rapl: Fix the energy-pkg event for AMD CPUs Dhananjay Ugwekar
2024-09-04 12:48 ` Liang, Kan
2024-09-05 10:07 ` Ingo Molnar [this message]
2024-09-05 14:30 ` Liang, Kan
2024-09-09 6:44 ` Dhananjay Ugwekar
2024-09-09 9:32 ` Ingo Molnar
2024-09-10 9:01 ` Dhananjay Ugwekar
2024-09-05 10:13 ` [tip: perf/urgent] " tip-bot2 for Dhananjay Ugwekar
2024-09-05 12:19 ` [PATCH v3] " Dhananjay Ugwekar
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=ZtmC8hhpUvQTXFDn@gmail.com \
--to=mingo@kernel.org \
--cc=Dhananjay.Ugwekar@amd.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gautham.shenoy@amd.com \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--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=tglx@linutronix.de \
--cc=x86@kernel.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 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.