From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Anton Blanchard <anton@samba.org>
Cc: Matthew Wilcox <willy@debian.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@osdl.org>
Subject: Re: pci_domain_nr vs. /sys/devices
Date: Tue, 17 Jun 2003 13:41:56 +0400 [thread overview]
Message-ID: <20030617134156.A2473@jurassic.park.msu.ru> (raw)
In-Reply-To: <20030617044948.GA1172@krispykreme>; from anton@samba.org on Tue, Jun 17, 2003 at 02:49:48PM +1000
On Tue, Jun 17, 2003 at 02:49:48PM +1000, Anton Blanchard wrote:
> And only creates /proc/bus/pci entries for the first domain.
Err, this definitely breaks X on alpha. On small and mid-range
machines we always have pci_domain_nr(bus) == bus->number.
Practically, it's only Marvel where we could overflow an 8-bit
bus number.
> Finally there was some shuffling required to make pci_bus_exists work
> (passing in a pci_bus *, ->sysdata and ->number must be initialised
> before calling it). There are some uses of pci_bus_exists in x86 that
> will need updating.
>
> Thoungts?
Looks good to me, except this (see above):
> + /* Backwards compatibility for domain 0 only */
> + if (pci_domain_nr(dev->bus) != 0)
> + return 0;
How about this instead?
/* Backwards compatibility for first N PCI domains. */
if (pci_domain_nr(dev->bus) > PCI_PROC_MAX_DOMAIN)
return 0;
PCI_PROC_MAX_DOMAIN could be defined in asm/pci.h (255 on alpha), default 0.
Ivan.
next prev parent reply other threads:[~2003-06-17 9:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 14:30 Benjamin Herrenschmidt
2003-06-11 14:48 ` Matthew Wilcox
2003-06-11 15:06 ` Benjamin Herrenschmidt
2003-06-11 15:12 ` Matthew Wilcox
2003-06-11 15:40 ` Russell King
2003-06-11 16:00 ` Benjamin Herrenschmidt
2003-06-17 4:52 ` Anton Blanchard
2003-06-11 17:03 ` Patrick Mochel
2003-06-17 4:49 ` Anton Blanchard
2003-06-17 9:41 ` Ivan Kokshaysky [this message]
2003-06-17 12:49 ` Anton Blanchard
2003-06-17 13:11 ` Ivan Kokshaysky
2003-06-17 19:42 ` Matthew Wilcox
2003-06-17 21:30 ` Ivan Kokshaysky
2003-06-18 13:02 ` Matthew Wilcox
2003-06-18 13:24 ` Ivan Kokshaysky
2003-06-17 13:55 ` Matthew Wilcox
2003-06-17 16:25 ` Matthew Wilcox
2003-06-17 18:39 ` Olaf Hering
2003-06-11 15:42 ` Russell King
2003-06-12 0:37 ` Anton Blanchard
2003-06-12 13:27 ` Benjamin Herrenschmidt
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=20030617134156.A2473@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=willy@debian.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
all inboxes | Powered by JetHome®