From: Yinghai Lu <yinghai@kernel.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Yinghai Lu <yinghai@kernel.org>
Subject: [RFC PATCH 0/3] PCI: allocate pci bus num range for bridge scan
Date: Sat, 21 Jan 2012 02:24:05 -0800 [thread overview]
Message-ID: <1327141448-15281-1-git-send-email-yinghai@kernel.org> (raw)
2632ed3: PCI: kill pci_fixup_parent_subordinate_busnr()
5b951ec: PCI: Allocate bus range instead of use max blindly
b9459d8: PCI: Add iobusn_resource and insert root bus range to that tree.
set up iobusn_resource tree, and register bus number range it.
later when need to find bus range, will try to allocate from the tree
need to test on arches other than x86, to verify if root bus end finding
is right.
could be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci-busn-alloc
Thanks
Yinghai
arch/ia64/pci/pci.c | 9 +
arch/powerpc/kernel/pci-common.c | 12 ++-
arch/x86/include/asm/topology.h | 3 +-
arch/x86/pci/acpi.c | 15 ++-
arch/x86/pci/bus_numa.c | 8 +-
arch/x86/pci/common.c | 11 +-
drivers/parisc/dino.c | 9 +
drivers/parisc/lba_pci.c | 8 +
drivers/pci/probe.c | 298 +++++++++++++++++++++++++++++---------
drivers/pci/remove.c | 1 +
include/linux/ioport.h | 1 +
include/linux/pci.h | 5 +
kernel/resource.c | 8 +
13 files changed, 310 insertions(+), 78 deletions(-)
next reply other threads:[~2012-01-21 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 10:24 Yinghai Lu [this message]
2012-01-21 10:24 ` [RFC PATCH 1/3] PCI: Add iobusn_resource and insert root bus range to that tree Yinghai Lu
2012-01-21 10:24 ` [RFC PATCH 2/3] PCI: Allocate bus range instead of use max blindly Yinghai Lu
2012-01-21 10:24 ` [RFC PATCH 3/3] PCI: kill pci_fixup_parent_subordinate_busnr() Yinghai Lu
2012-01-22 19:22 ` [RFC PATCH 0/3] PCI: allocate pci bus num range for bridge scan Yinghai Lu
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=1327141448-15281-1-git-send-email-yinghai@kernel.org \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).