public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/1] ARM64/PCI: ACPI NUMA node set-up
Date: Wed, 24 May 2017 18:22:18 +0100	[thread overview]
Message-ID: <20170524172219.5689-1-lorenzo.pieralisi@arm.com> (raw)

This patch series is v3 of a previous posting:

v2 -> v3

- Dropped generic approach
  # It was not consistent between ACPI and DT and not reusable on x86/IA64
- Trimmed the series to one patch ARM64 specific, three-line patch fixes
  the issue
- Rebased against v4.12-rc2
- Dropped RFC/RFT tag

v2: https://lkml.org/lkml/2017/5/15/433

v1 -> v2:

- Added missing call to acpi_pci_bus_find_numa_node()
- Rebased against v4.12-rc1

v1: https://lkml.org/lkml/2017/4/26/211

--- Original Cover Letter --

On the ARM64 architecture, the arch specific PCI pcibus_to_node() callback
can be triggered on struct pci_bus.sysdata structures that carry host
bridge specific data through different structures layout (ie sysdata
pointer points at different structs for different host bridges), therefore
it is not possible to have a unified pcibus_to_node() implementation.

Given that the device NUMA node is a property of the struct pci_bus (and
its associated struct device), move the struct pci_bus node assignment to
generic PCI code, where according to the platform firmware the NUMA node
for the device backing the struct pci_bus is retrieved and propagated
through the PCI bus hierarchy.

Lorenzo Pieralisi (1):
  ARM64/PCI: Set root bus NUMA node on ACPI systems

 arch/arm64/kernel/pci.c | 3 +++
 1 file changed, 3 insertions(+)

-- 
2.10.0

             reply	other threads:[~2017-05-24 17:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 17:22 Lorenzo Pieralisi [this message]
2017-05-24 17:22 ` [PATCH v3 1/1] ARM64/PCI: Set root bus NUMA node on ACPI systems Lorenzo Pieralisi
2017-05-29  8:32   ` Robert Richter
2017-05-30 10:47   ` Will Deacon

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=20170524172219.5689-1-lorenzo.pieralisi@arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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