[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241210163734.GA3244835@bhelgaas>
Date: Tue, 10 Dec 2024 10:37:34 -0600
From: Bjorn Helgaas <helgaas@...nel.org>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: "Meyer, Kyle" <kyle.meyer@....com>,
"Zhuo, Qiuxu" <qiuxu.zhuo@...el.com>, "bp@...en8.de" <bp@...en8.de>,
"james.morse@....com" <james.morse@....com>,
"mchehab@...nel.org" <mchehab@...nel.org>,
"rric@...nel.org" <rric@...nel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] EDAC/{i10nm,skx,skx_common}: Support multiple clumps
On Fri, Dec 06, 2024 at 10:09:23PM +0000, Luck, Tony wrote:
> What we need here is a function that maps from a PCIe device to a CPU socket.
>
> Has this problem been encountered before? Is there an existing solution?
There's nothing in PCI itself that connects a device to a CPU. It
sounds like something that might fit with an ACPI NUMA description,
e.g., if a CPU and a PCI host bridge had the same ACPI _PXM value, you
could conclude that the devices below the host bridge are close to the
CPU.
Bjorn
Powered by blists - more mailing lists