From: Sinan Kaya <okaya@codeaurora.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: acpi: Support PCI devices numa_node property in ACPI mode
Date: Wed, 12 Apr 2017 13:48:15 -0400 [thread overview]
Message-ID: <5f01eac0-37a2-392e-eb42-a9ac85a2eebc@codeaurora.org> (raw)
In-Reply-To: <855540a9-888d-6419-3add-d8b0dbb43029@codeaurora.org>
On 4/12/2017 1:27 PM, Sinan Kaya wrote:
> I am not a big fan of this. I wonder if we could not make it DT/ACPI
> agnostic by simply setting the numa_node in the pci_bus->dev field,
> and propagate it downstream a PCI hierarcy (as we do with sysdata)
> in pci_alloc_child_bus().
I didn't realize that we were pushing sysdata to the child buses. No
issues then.
I was under the impression that sysdata only existed for the host bridge
itself and was not shared with the rest of the bus.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-04-12 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 17:17 [PATCH] arm64: acpi: Support PCI devices numa_node property in ACPI mode Sinan Kaya
2017-04-12 17:04 ` Lorenzo Pieralisi
2017-04-12 17:27 ` Sinan Kaya
2017-04-12 17:48 ` Sinan Kaya [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-06 11:47 Sergey Temerkhanov
2017-04-07 17:18 ` Lorenzo Pieralisi
2017-04-07 18:31 ` Sergei Temerkhanov
2017-04-21 17:17 ` 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=5f01eac0-37a2-392e-eb42-a9ac85a2eebc@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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).