From: Sam Bobroff <sbobroff@linux.ibm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Alistair Popple <alistair@popple.id.au>,
kvm-ppc@vger.kernel.org, Oliver O'Halloran <oohall@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH kernel] powerpc/pci/of: Parse unassigned resources
Date: Tue, 18 Jun 2019 14:02:38 +1000 [thread overview]
Message-ID: <20190618040237.GA4735@tungsten.ozlabs.ibm.com> (raw)
In-Reply-To: <a9f5d1d7-a8dc-91eb-8197-a7aa9b45957b@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 3749 bytes --]
On Fri, Jun 14, 2019 at 01:18:28PM +1000, Alexey Kardashevskiy wrote:
>
>
> On 14/06/2019 12:59, Alexey Kardashevskiy wrote:
> > The pseries platform uses the PCI_PROBE_DEVTREE method of PCI probing
> > which is basically reading "assigned-addresses" of every PCI device.
> > However if the property is missing or zero sized, then there is
> > no fallback of any kind and the PCI resources remain undiscovered, i.e.
> > pdev->resource[] array is empty.
> >
> > This adds a fallback which parses the "reg" property in pretty much same
> > way except it marks resources as "unset" which later makes Linux assign
> > those resources with proper addresses.
> >
> > Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> > ---
> >
> > This is an attempts to boot linux directly under QEMU without slof/rtas;
> > the aim is to use petitboot instead and let the guest kernel configure
> > devices.
> >
> > QEMU does not allocate resources, it creates correct "reg" and zero length
> > "assigned-addresses" (which is probably a bug on its own) which is
> > normally populated by SLOF later but not during this exercise.
Hi Alexey,
This patch (fixed, as you point out below) also seems to improve hotplug
on pSeries.
Currently, the PCI hotplug driver for pSeries (rpaphp) uses generic PCI
scanning to add hot plugged devices, rather than slot power control,
because the slot power control method doesn't work.
AFAIK one of the reasons that slot power control doesn't work is that
the assigned-addresses node isn't populated by QEMU during hotplug, so I
tested this patch on a guest that has been modified to use that method.
In combination with a QEMU change to prevent PCI_PROBE_ONLY being set
(necessary to allow pcibios_finish_adding_to_bus() to do resource
allocation -- I assume you are using a similar change), I was able to
successfully hot plug a few devices!
So this change seems to be a step in the right direction.
(I also tested it with an unmodified guest, and it doesn't seem to harm
hotpluging via generic PCI scanning.)
One nit: I think that calling the variable "unset" is a bit confusing.
What about calling it "aa_missing" or something like that?
Cheers,
Sam.
> > ---
> > arch/powerpc/kernel/pci_of_scan.c | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/arch/powerpc/kernel/pci_of_scan.c b/arch/powerpc/kernel/pci_of_scan.c
> > index 64ad92016b63..cfe6ec3c6aaf 100644
> > --- a/arch/powerpc/kernel/pci_of_scan.c
> > +++ b/arch/powerpc/kernel/pci_of_scan.c
> > @@ -82,10 +82,18 @@ static void of_pci_parse_addrs(struct device_node *node, struct pci_dev *dev)
> > const __be32 *addrs;
> > u32 i;
> > int proplen;
> > + bool unset = false;
> >
> > addrs = of_get_property(node, "assigned-addresses", &proplen);
> > if (!addrs)
> > return;
>
>
> Ah. Of course, these 2 lines above should go, my bad. I'll repost if
> there are no other (and bigger) problems with this.
>
>
>
> > + if (!addrs || !proplen) {
> > + addrs = of_get_property(node, "reg", &proplen);
> > + if (!addrs || !proplen)
> > + return;
> > + unset = true;
> > + }
> > +
> > pr_debug(" parse addresses (%d bytes) @ %p\n", proplen, addrs);
> > for (; proplen >= 20; proplen -= 20, addrs += 5) {
> > flags = pci_parse_of_flags(of_read_number(addrs, 1), 0);
> > @@ -110,6 +118,8 @@ static void of_pci_parse_addrs(struct device_node *node, struct pci_dev *dev)
> > continue;
> > }
> > res->flags = flags;
> > + if (unset)
> > + res->flags |= IORESOURCE_UNSET;
> > res->name = pci_name(dev);
> > region.start = base;
> > region.end = base + size - 1;
> >
>
> --
> Alexey
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-18 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 2:59 [PATCH kernel] powerpc/pci/of: Parse unassigned resources Alexey Kardashevskiy
2019-06-14 3:18 ` Alexey Kardashevskiy
2019-06-18 4:02 ` Sam Bobroff [this message]
2019-06-18 12:15 ` Michael Ellerman
2019-06-18 12:29 ` Benjamin Herrenschmidt
2019-06-19 1:20 ` Alexey Kardashevskiy
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=20190618040237.GA4735@tungsten.ozlabs.ibm.com \
--to=sbobroff@linux.ibm.com \
--cc=aik@ozlabs.ru \
--cc=alistair@popple.id.au \
--cc=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@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).