[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQVG9YbZW=Usv0drxuyQ=ZTERK5KZK3TF6aX-iWuAS8L6Q@mail.gmail.com>
Date: Fri, 3 Feb 2012 18:30:42 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Tony Luck <tony.luck@...el.com>,
Dominik Brodowski <linux@...inikbrodowski.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org
Subject: Re: [PATCH 02/15] PCI: Add iobusn_resource
On Fri, Feb 3, 2012 at 3:38 PM, Benjamin Herrenschmidt
<benh@...nel.crashing.org> wrote:
> On Fri, 2012-02-03 at 08:36 -0800, Bjorn Helgaas wrote:
>> On Wed, Feb 1, 2012 at 2:43 PM, Yinghai Lu <yinghai@...nel.org> wrote:
>> > also add busn_res into struct pci_bus.
>> >
>> > will use them to have bus number resource tree.
>>
>> Will you make this tree visible in /proc? Seems like that would be
>> useful for debugging and for symmetry with /proc/iomem and
>> /proc/ioports.
>
> To be honest that whole business with bus numbers in struct resource
> seems like gratuituous bloat & over engineering to me ...
ah, i thought it is simple enough, and should be done before already.
> Does it actually solve a specific problem or serve a purpose ?
very beginning is for one IBM x3950...
https://bugzilla.novell.com/show_bug.cgi?id=735909
++max searching valid bus number range is out of boundary of peer root
bus range.
later, found the code could help: pcie hotplug, pci bus rescan and
even remove some hacks for/from cardbus field.
now with this patchset (+ one patch that is not sent out yet), I could
even use setpci/pci rescan to move pci bus around.
Thanks
Yinghai
--
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