From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: <bhelgaas@google.com>
Cc: <lorenzo.pieralisi@arm.com>, <linux-pci@vger.kernel.org>,
<linuxarm@huawei.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [PATCH 0/1] PCI: support numa node specification on a per device basis.
Date: Wed, 12 Sep 2018 16:21:39 +0100 [thread overview]
Message-ID: <20180912152140.3676-1-Jonathan.Cameron@huawei.com> (raw)
The ACPI specification allows individual PCI devices to be associated
with proximity domains that may or may not be the same as the host bridge
below which they are attached. This is done with the _PXM method.
Unfortunately Linux doesn't take any notice of this as it would normally
be done during the device_add but that stage the ACPI firmware node
is not yet associated with the device as this is not done until the
call to acpi_pci_find_companion which is called form acpi_platform_notify
only after the device_add.
The easiest place to make this association seems to be pci_acpi_setup,
but there are lots of alternative possibilities.
Jonathan Cameron (1):
pci: Pick up the acpi numa node value if it is specified at the device
level.
drivers/pci/pci-acpi.c | 5 +++++
1 file changed, 5 insertions(+)
--
2.18.0
next reply other threads:[~2018-09-12 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 15:21 Jonathan Cameron [this message]
2018-09-12 15:21 ` [PATCH 1/1] pci: Pick up the acpi numa node value if it is specified at the device level Jonathan Cameron
2018-09-12 17:32 ` Bjorn Helgaas
[not found] ` <e4bd3423-ae2a-262c-1391-f9741ac4fdd0@geanix.com>
2018-11-13 9:24 ` Jonathan Cameron
2018-11-13 9:33 ` Jonathan Cameron
[not found] ` <8a0fd569-fa52-b884-ef0d-18aab1ef8c3f@geanix.com>
2018-11-13 10:23 ` Jonathan Cameron
2018-11-13 10:26 ` Martin Hundebøll
2018-11-13 14:49 ` Jonathan Cameron
[not found] ` <c02e2579-3572-533d-2c14-b7fe35a1057b@geanix.com>
2018-11-14 8:57 ` Jonathan Cameron
2018-11-14 9:31 ` Martin Hundebøll
2018-11-15 10:24 ` Jonathan Cameron
2018-11-15 10:30 ` Martin Hundebøll
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=20180912152140.3676-1-Jonathan.Cameron@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.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).