From: "Chen, Zide" <zide.chen@intel.com>
To: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Eranian Stephane <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Xudong Hao <xudong.hao@intel.com>,
Falcon Thomas <thomas.falcon@intel.com>,
Steve Wahl <steve.wahl@hpe.com>
Subject: Re: [PATCH V2 1/2] perf/x86/intel/uncore: Skip discovery table for offline dies
Date: Thu, 15 Jan 2026 10:24:38 -0800 [thread overview]
Message-ID: <d263cc20-6e6c-47c4-9a9b-0d9b4221322e@intel.com> (raw)
In-Reply-To: <a2723541-ee60-4793-8376-b1247e72ae86@linux.intel.com>
On 1/13/2026 6:31 PM, Mi, Dapeng wrote:
>
> On 1/14/2026 4:56 AM, Zide Chen wrote:
>> This warning can be triggered if NUMA is disabled and the system
>> boots with fewer CPUs than the number of CPUs in die 0.
>>
>> WARNING: CPU: 9 PID: 7257 at uncore.c:1157 uncore_pci_pmu_register+0x136/0x160 [intel_uncore]
>>
>> Currently, the discovery table continues to be parsed even if all CPUs
>> in the associated die are offline. This can lead to an array overflow
>> at "pmu->boxes[die] = box" in uncore_pci_pmu_register(), which may
>> trigger the warning above or cause other issues.
>>
>> Reported-by: Steve Wahl <steve.wahl@hpe.com>
>> Tested-by: Steve Wahl <steve.wahl@hpe.com>
>> Fixes: edae1f06c2cd ("perf/x86/intel/uncore: Parse uncore discovery tables")
>> Signed-off-by: Zide Chen <zide.chen@intel.com>
>> ---
>> V2:
>> - Add the Tested-by tag
>> - Rebase onto perf/core (base commit: a491c02c2770)
>>
>> arch/x86/events/intel/uncore.c | 4 ++++
>> arch/x86/events/intel/uncore_discovery.c | 2 +-
>> 2 files changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/events/intel/uncore.c b/arch/x86/events/intel/uncore.c
>> index 4684649109d9..c126a29ab729 100644
>> --- a/arch/x86/events/intel/uncore.c
>> +++ b/arch/x86/events/intel/uncore.c
>> @@ -1368,6 +1368,10 @@ static void uncore_pci_pmus_register(void)
>>
>> for (node = rb_first(type->boxes); node; node = rb_next(node)) {
>> unit = rb_entry(node, struct intel_uncore_discovery_unit, node);
>> +
>> + if (WARN_ON(unit->die >= uncore_max_dies()))
>> + continue;
>
> I'm thinking if we need to add "WARN_ON" here. Since all uncore units that
> the die id is larger than uncore_max_dies() would be skipped in discovery
> phase, the unit die id should be not larger than uncore_max_dies() in
> uncore_pci_pmus_register(). Is it right?
I originally added this as a defensive check in case it could trigger an
array overflow.
However, I agree it can be dropped since this condition should not be
reachable.
>> +
>> pdev = pci_get_domain_bus_and_slot(UNCORE_DISCOVERY_PCI_DOMAIN(unit->addr),
>> UNCORE_DISCOVERY_PCI_BUS(unit->addr),
>> UNCORE_DISCOVERY_PCI_DEVFN(unit->addr));
>> diff --git a/arch/x86/events/intel/uncore_discovery.c b/arch/x86/events/intel/uncore_discovery.c
>> index b46575254dbe..0e414cecb6f2 100644
>> --- a/arch/x86/events/intel/uncore_discovery.c
>> +++ b/arch/x86/events/intel/uncore_discovery.c
>> @@ -366,7 +366,7 @@ static bool uncore_discovery_pci(struct uncore_discovery_domain *domain)
>> (val & UNCORE_DISCOVERY_DVSEC2_BIR_MASK) * UNCORE_DISCOVERY_BIR_STEP;
>>
>> die = get_device_die_id(dev);
>> - if (die < 0)
>> + if ((die < 0) || (die >= uncore_max_dies()))
>> continue;
>>
>> parse_discovery_table(domain, dev, die, bar_offset, &parsed);
prev parent reply other threads:[~2026-01-15 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 20:56 [PATCH V2 1/2] perf/x86/intel/uncore: Skip discovery table for offline dies Zide Chen
2026-01-13 20:56 ` [PATCH V2 2/2] perf/x86/intel/uncore: Fix die ID init and look up bugs Zide Chen
2026-01-14 5:19 ` Mi, Dapeng
2026-01-15 18:17 ` Chen, Zide
2026-01-14 2:31 ` [PATCH V2 1/2] perf/x86/intel/uncore: Skip discovery table for offline dies Mi, Dapeng
2026-01-15 18:24 ` Chen, Zide [this message]
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=d263cc20-6e6c-47c4-9a9b-0d9b4221322e@intel.com \
--to=zide.chen@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.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 \
--cc=steve.wahl@hpe.com \
--cc=thomas.falcon@intel.com \
--cc=xudong.hao@intel.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