From: "David S. Miller" <davem@redhat.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Tom Gall <tom_gall@vnet.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: Going beyond 256 PCI buses
Date: Thu, 14 Jun 2001 07:42:29 -0700 (PDT) [thread overview]
Message-ID: <15144.52565.566355.291642@pizda.ninka.net> (raw)
In-Reply-To: <3B28CB1A.E8226801@mandrakesoft.com>
In-Reply-To: <3B273A20.8EE88F8F@vnet.ibm.com> <3B28C6C1.3477493F@mandrakesoft.com> <15144.51504.8399.395200@pizda.ninka.net> <3B28CB1A.E8226801@mandrakesoft.com>
Jeff Garzik writes:
> Why do you want to make the bus number larger than the PCI bus number
> register?
This isn't it. What I'm trying to provoke thought on is
"is there a way to make mindless apps using these syscalls
work transparently"
I think the answer is no. Apps should really fetch info out
of /proc/bus/pci and use the controller ioctl.
But someone could surprise me :-)
> It seems like adding 'unsigned int domain_num' makes more sense, and is
> more correct. Maybe that implies fixing up other code to use a
> (domain,bus) pair, but that's IMHO a much better change than totally
> changing the interpretation of pci_bus::bus_number...
Correct, I agree. But I don't even believe we should be sticking
the domain thing into struct pci_bus.
It's a platform thing. Most platforms have a single domain, so why
clutter up struct pci_bus with this value? By this reasoning we could
say that since it's arch-specific, this stuff belongs in sysdata or
wherever.
And this is what is happening right now. So in essence, the work is
done :-) The only "limiting factor" is that x86 doesn't support
multiple domains as some other platforms do. So all these hot-plug
patches just need to use domains properly, and perhaps add domain
support to X86 when one of these hot-plug capable controllers are
being used.
> > 2) Figure out what to do wrt. sys_pciconfig_{read,write}()
>
> 3) (tiny issue) Change pci_dev::slot_name such that it includes the
> domain number. This is passed to userspace by SCSI and net drivers as a
> way to allow userspace to associate a kernel interface with a bus
> device.
Sure. It's an address and the domain is part of the address.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-06-14 14:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 10:02 Going beyond 256 PCI buses Tom Gall
2001-06-13 17:17 ` Albert D. Cahalan
2001-06-13 18:29 ` Tom Gall
2001-06-14 14:14 ` Jeff Garzik
2001-06-14 15:15 ` David S. Miller
2001-06-14 17:59 ` Jonathan Lundell
2001-06-14 20:50 ` Jonathan Lundell
2001-06-14 14:24 ` David S. Miller
2001-06-14 14:32 ` Jeff Garzik
2001-06-14 14:42 ` David S. Miller [this message]
2001-06-14 15:29 ` Jeff Garzik
2001-06-14 15:33 ` Jeff Garzik
2001-06-14 18:01 ` Albert D. Cahalan
2001-06-14 18:47 ` David S. Miller
2001-06-14 19:04 ` Albert D. Cahalan
2001-06-14 19:12 ` David S. Miller
2001-06-14 19:41 ` Jeff Garzik
2001-06-14 19:57 ` David S. Miller
2001-06-14 20:08 ` Jeff Garzik
2001-06-14 20:14 ` David S. Miller
2001-06-14 21:30 ` Benjamin Herrenschmidt
2001-06-14 21:46 ` Jeff Garzik
2001-06-14 21:48 ` David S. Miller
2001-06-14 21:57 ` Benjamin Herrenschmidt
2001-06-14 22:12 ` David S. Miller
2001-06-14 22:29 ` Benjamin Herrenschmidt
2001-06-14 22:49 ` David S. Miller
2001-06-14 23:35 ` Benjamin Herrenschmidt
2001-06-14 23:35 ` VGA handling was [Re: Going beyond 256 PCI buses] James Simmons
2001-06-14 23:42 ` David S. Miller
2001-06-14 23:55 ` James Simmons
2001-06-15 15:14 ` Pavel Machek
2001-06-15 2:06 ` Albert D. Cahalan
2001-06-15 8:52 ` Matan Ziv-Av
2001-06-14 21:35 ` Going beyond 256 PCI buses David S. Miller
2001-06-14 21:46 ` Benjamin Herrenschmidt
2001-06-16 21:32 ` Jeff Garzik
2001-06-16 23:29 ` Benjamin Herrenschmidt
2001-06-15 8:42 ` Geert Uytterhoeven
2001-06-15 15:38 ` David S. Miller
2001-06-14 19:03 ` David S. Miller
2001-06-14 20:56 ` David S. Miller
2001-06-14 15:13 ` Jonathan Lundell
2001-06-14 15:17 ` 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=15144.52565.566355.291642@pizda.ninka.net \
--to=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;
as well as URLs for NNTP newsgroup(s).