[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAErSpo4U6orULckFofbJON+x70m1G4w76rK4Y1Besh_K-m612g@mail.gmail.com>
Date: Thu, 25 Aug 2011 17:23:24 -0600
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: Deng-Cheng Zhu <dengcheng.zhu@...il.com>
Cc: jbarnes@...tuousgeek.org, ralf@...ux-mips.org,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mips@...ux-mips.org, eyal@...s.com, zenon@...s.com
Subject: Re: [RFC PATCH 1/3] MIPS: PCI: Use pci_bus_remove_resources()/pci_bus_add_resource()
to set up root resources
On Thu, Aug 25, 2011 at 5:14 PM, Deng-Cheng Zhu <dengcheng.zhu@...il.com> wrote:
> 2011/8/25 Bjorn Helgaas <bhelgaas@...gle.com>:
>> No, I just mean that I don't see why you need this patch at all. If
>> you pass the list of bus resources to pci_create_bus(), there's no
>> need to fix anything up later. Or am I missing something?
>
> Well, doing the root resource fixups in here is a *paranoid* way. It's to
> deal with the 'unlikely' circumstance where controller_resources() returns
> the NULL pointer in pcibios_scanbus() due to memory allocation failure.
> Most of the time (always) it's nothing more than repeating the resource
> list setup. But maybe we can do something like this:
>
> if (unlikely(!dev && list_empty(&bus->resources))
> pcibios_setup_root_resources(bus, hose);
>
>
> What do you think?
I don't think it's worth it. Just check for failure of
controller_resources(), and if it fails, skip the pci_create_bus()
call. You've already printed a message (you might add the PCI
domain/bus number).
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists