From: Richard Henderson <rth@twiddle.net>
To: Tom Gall <tom_gall@vnet.ibm.com>
Cc: "David S. Miller" <davem@redhat.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
linux-kernel@vger.kernel.org
Subject: Re: RFC: Changes for PCI
Date: Thu, 28 Jun 2001 22:22:01 -0700 [thread overview]
Message-ID: <20010628222201.A2521@twiddle.net> (raw)
In-Reply-To: <3B3A58FC.2728DAFF@vnet.ibm.com> <3B3A5B00.9FF387C9@mandrakesoft.com> <3B3A64CD.28B72A2A@vnet.ibm.com> <15162.33332.781686.45753@pizda.ninka.net> <3B3A2EF9.4A44264F@vnet.ibm.com>
In-Reply-To: <3B3A2EF9.4A44264F@vnet.ibm.com>; from tom_gall@vnet.ibm.com on Wed, Jun 27, 2001 at 02:07:37PM -0500
On Wed, Jun 27, 2001 at 02:07:37PM -0500, Tom Gall wrote:
> Consider also in drivers/pci/pci.c:
>
> The function pci_bus_exists checks based on bus numbers. This function is
> of course used by pci_alloc_primary_bus, which is in turn used by
> pci_scan_bus. As is today, this code can break me the second I'm
> onto my second PCI system domain.
You'll find that the existing ports that support multiple pci
domains do not number the busses on the secondary domains from
zero. If domain 0 has 3 busses, then domain 1's root bus will
be bus number 3, and so on.
This approach works quite well in practice, even on machines
with large numbers of pci domains, since there tends to be no
pci-pci busses on domains other than the one containing legacy
i/o widgetry.
r~
next prev parent reply other threads:[~2001-06-29 5:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 22:06 RFC: Changes for PCI Tom Gall
2001-06-27 22:15 ` Jeff Garzik
2001-06-27 22:57 ` Tom Gall
2001-06-27 23:34 ` Jeff Garzik
2001-06-27 18:24 ` Tom Gall
2001-06-28 20:57 ` Gérard Roudier
2001-06-28 21:11 ` Tom Gall
2001-06-28 21:18 ` Jeff Garzik
2001-06-28 21:12 ` Jeff Garzik
2001-06-28 1:02 ` David S. Miller
2001-06-27 19:07 ` Tom Gall
2001-06-29 5:22 ` Richard Henderson [this message]
2001-06-29 3:14 ` Tom Gall
2001-06-27 23:17 ` anton
2001-06-28 1:04 ` David S. Miller
2001-06-27 18:49 ` Tom Gall
2001-06-28 4:06 ` David S. Miller
2001-06-27 20:01 ` Tom Gall
[not found] ` <mailman.993682861.9307.linux-kernel2news@redhat.com>
2001-06-27 23:41 ` Pete Zaitcev
2001-06-28 0:48 ` David S. Miller
2001-06-28 1:00 ` David S. Miller
2001-06-27 23:12 ` anton
2001-06-28 0:59 ` David S. Miller
2001-06-28 16:48 ` Todd Inglett
2001-06-28 17:01 ` Jeff Garzik
2001-06-28 17:20 ` Todd Inglett
2001-06-28 17:01 ` Alan Cox
2001-06-28 21:54 ` Gérard Roudier
-- strict thread matches above, loose matches on Subject: below --
2001-06-28 23:08 Khachaturov, Vassilii
2001-06-28 23:27 ` Jeff Garzik
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=20010628222201.A2521@twiddle.net \
--to=rth@twiddle.net \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom_gall@vnet.ibm.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