From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>
Cc: linux-pci@vger.kernel.org, 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 1/3] PCI: Introduce pci_bus_find_numa_node()
Date: Mon, 15 May 2017 14:05:00 +0100 [thread overview]
Message-ID: <20170515130500.GA19201@red-moon> (raw)
In-Reply-To: <20170515125711.GA9700@localhost.localdomain>
On Mon, May 15, 2017 at 05:57:11AM -0700, Vadim Lomovtsev wrote:
> On Fri, May 12, 2017 at 10:18:46AM -0700, Vadim Lomovtsev wrote:
> Hi Lorenzo,
>
> > Hi Lorenzo
> >
> > On Fri, May 12, 2017 at 04:50:40PM +0100, Lorenzo Pieralisi wrote:
> > > Hi Vadim,
> > >
> > > On Fri, May 12, 2017 at 05:44:05AM -0700, Vadim Lomovtsev wrote:
> > > > Hi Lorenzo,
> > > >
> > > > Are there any news related to these patches ?
> > >
> > > Not really, I have not received any feedback but I was expecting some
> > > to make progress here. Have you tested it ?
> > >
> > > Please let me know, thanks !
> >
> > Not yet. Plan to test them after weekend and will get back to you.
> >
>
> Here is the results of testing you patches at dual-socketed board
> with Cavium ThunderX SoC.
>
> Each boot kernel boot with acpi=force argument.
>
> 1. The 4.12-rc1 couldn't find rootfs partition so can't be tested.
> 2.1 The 4.11 without your patch set 0 to numa node for pci device
> cat /sys/bus/pci/devices/*/numa_node
> got zeroes here for all devices
> 2.2 The 4.11 with your patches applied set -1 to numa_node for all pci devices
> same command provides "-1"
>
> So looking at your patches..
>
> At the patch 1/3 you implemented pci_bus_find_numa_node function:
>
> +int pci_bus_find_numa_node(struct pci_bus *bus)
> +{
> + return NUMA_NO_NODE;
> +}
>
> Then at the 2/3 patch it is called from pci_register_host_bridge:
> @@ -770,6 +770,7 @@ int pci_register_host_bridge(struct pci_host_bridge *bridge)
> [..]
> + set_dev_node(&bus->dev, pci_bus_find_numa_node(bus));
>
> I suppose that is why I'm seeing those -1 in the numa_node field.
>
> And at the patch 3/3 you implemented acpi_pci_bus_find_numa_node function
> +int acpi_pci_bus_find_numa_node(struct pci_bus *bus)
> which implements actual work of getting numa node value,
> but it seems that nodoby calls it, isn't it ?
>
> Don't we need to update pci_bus_find_numa_node with proper calling
> of acpi_pci_bus_find_numa_node() ?
Yes:
https://lkml.org/lkml/2017/4/26/211
Apologies for wasting your time, v2 coming with the actual call,
please have a look.
Thanks,
Lorenzo
prev parent reply other threads:[~2017-05-15 13:04 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
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 [this message]
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=20170515130500.GA19201@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=Vadim.Lomovtsev@caviumnetworks.com \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).