From: Zhou Wang <wangzhou1@hisilicon.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
<linux-pci@vger.kernel.org>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
Sergey Temerkhanov <s.temerkhanov@gmail.com>,
Sinan Kaya <okaya@codeaurora.org>
Subject: Re: [RFC/RFT PATCH 3/3] PCI/ACPI: Add ACPI pci_bus_find_numa_node() implementation
Date: Mon, 15 May 2017 14:13:47 +0800 [thread overview]
Message-ID: <5919471B.7080607@hisilicon.com> (raw)
In-Reply-To: <20170426100619.31758-3-lorenzo.pieralisi@arm.com>
On 2017/4/26 18:06, Lorenzo Pieralisi wrote:
> The introduction of pci_bus_find_numa_node(pci_bus) allows at PCI
> host bridge registration to detect the NUMA node for a given
> struct pci_bus.dev. Implement an ACPI method that, through
> the struct pci_bus.bridge ACPI companion, retrieve and return
> the NUMA node corresponding to a given struct pci_bus.dev.
>
> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> ---
> drivers/pci/pci-acpi.c | 20 ++++++++++++++++++++
> include/linux/pci.h | 6 ++++++
> 2 files changed, 26 insertions(+)
>
> diff --git a/drivers/pci/pci-acpi.c b/drivers/pci/pci-acpi.c
> index 0018603..915da79 100644
> --- a/drivers/pci/pci-acpi.c
> +++ b/drivers/pci/pci-acpi.c
> @@ -10,6 +10,7 @@
> #include <linux/delay.h>
> #include <linux/init.h>
> #include <linux/irqdomain.h>
> +#include <linux/numa.h>
> #include <linux/pci.h>
> #include <linux/msi.h>
> #include <linux/pci_hotplug.h>
> @@ -853,6 +854,25 @@ struct irq_domain *pci_host_bridge_acpi_msi_domain(struct pci_bus *bus)
> return irq_find_matching_fwnode(fwnode, DOMAIN_BUS_PCI_MSI);
> }
>
> +int acpi_pci_bus_find_numa_node(struct pci_bus *bus)
> +{
> + int node = NUMA_NO_NODE;
> + struct device *bridge = get_device(bus->bridge);
> +
> + if (!bridge)
> + return node;
> +
> + if (has_acpi_companion(bridge)) {
> + struct acpi_device *adev = to_acpi_device_node(bridge->fwnode);
> +
> + node = acpi_get_node(adev->handle);
> + }
> +
> + put_device(bridge);
> +
> + return node;
> +}
> +
It seems there is no function to call this, am I right?
Another question is that:
in the latest IORT revision C, "Proximity domain" has been added to the IORT spec.
So when we enable NUMA for a PCIe device, should we also consider this?
Thanks,
Zhou
> static int __init acpi_pci_init(void)
> {
> int ret;
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index 9e62462..b40d095 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -1481,6 +1481,12 @@ static inline int acpi_pci_bus_find_domain_nr(struct pci_bus *bus)
> #endif
> int pci_bus_find_domain_nr(struct pci_bus *bus, struct device *parent);
> #endif
> +#ifdef CONFIG_ACPI
> +int acpi_pci_bus_find_numa_node(struct pci_bus *bus);
> +#else
> +static inline int acpi_pci_bus_find_numa_node(struct pci_bus *bus)
> +{ return NUMA_NO_NODE; }
> +#endif
> int pci_bus_find_numa_node(struct pci_bus *bus);
>
> /* some architectures require additional setup to direct VGA traffic */
>
next prev parent reply other threads:[~2017-05-15 6:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 10:06 [RFC/RFT PATCH 1/3] PCI: Introduce pci_bus_find_numa_node() Lorenzo Pieralisi
2017-04-26 10:06 ` [RFC/RFT PATCH 2/3] PCI: Add call to set-up NUMA node for struct pci_bus devices Lorenzo Pieralisi
2017-04-26 10:06 ` [RFC/RFT PATCH 3/3] PCI/ACPI: Add ACPI pci_bus_find_numa_node() implementation Lorenzo Pieralisi
2017-05-15 6:13 ` Zhou Wang [this message]
2017-05-15 9:17 ` Lorenzo Pieralisi
2017-05-16 3:22 ` Zhou Wang
2017-05-12 12:44 ` [RFC/RFT PATCH 1/3] PCI: Introduce pci_bus_find_numa_node() Vadim Lomovtsev
2017-05-12 15:50 ` Lorenzo Pieralisi
2017-05-12 17:18 ` Vadim Lomovtsev
2017-05-15 12:57 ` Vadim Lomovtsev
2017-05-15 13:05 ` Lorenzo Pieralisi
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=5919471B.7080607@hisilicon.com \
--to=wangzhou1@hisilicon.com \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=okaya@codeaurora.org \
--cc=s.temerkhanov@gmail.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