From: Bjorn Helgaas <helgaas@kernel.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Meyer, Kyle" <kyle.meyer@hpe.com>,
"Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>,
"bp@alien8.de" <bp@alien8.de>,
"james.morse@arm.com" <james.morse@arm.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"rric@kernel.org" <rric@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] EDAC/{i10nm,skx,skx_common}: Support multiple clumps
Date: Tue, 10 Dec 2024 10:37:34 -0600 [thread overview]
Message-ID: <20241210163734.GA3244835@bhelgaas> (raw)
In-Reply-To: <SJ1PR11MB60832217752DE71A4ED1054CFC312@SJ1PR11MB6083.namprd11.prod.outlook.com>
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
next prev parent reply other threads:[~2024-12-10 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 16:59 [PATCH] EDAC/{i10nm,skx,skx_common}: Support multiple clumps Kyle Meyer
2024-12-05 19:13 ` Luck, Tony
2024-12-05 20:05 ` Kyle Meyer
2024-12-05 22:52 ` Luck, Tony
2024-12-05 23:57 ` Luck, Tony
2024-12-06 0:57 ` Kyle Meyer
2024-12-06 1:26 ` Zhuo, Qiuxu
2024-12-06 2:33 ` Kyle Meyer
2024-12-06 21:24 ` Luck, Tony
2024-12-06 22:09 ` Luck, Tony
2024-12-10 16:37 ` Bjorn Helgaas [this message]
2024-12-10 17:50 ` Luck, Tony
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=20241210163734.GA3244835@bhelgaas \
--to=helgaas@kernel.org \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=kyle.meyer@hpe.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rric@kernel.org \
--cc=tony.luck@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