From: Tom Gall <tom_gall@vnet.ibm.com>
To: "Gérard Roudier" <groudier@club-internet.fr>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>, linux-kernel@vger.kernel.org
Subject: Re: RFC: Changes for PCI
Date: Thu, 28 Jun 2001 21:11:31 +0000 [thread overview]
Message-ID: <3B3B9D83.F95D4496@vnet.ibm.com> (raw)
In-Reply-To: <20010628223210.Q1578-100000@>
Gérard Roudier wrote:
>
> On Wed, 27 Jun 2001, Jeff Garzik wrote:
>
> > Tom Gall wrote:
> > > Well you have device drivers like the symbios scsi driver for instance that
> > > tries to determine if it's seen a card before. It does this by looking at the
> > > bus,dev etc numbers... It's quite reasonable for two different scsi cards to be
> > > on the same bus number, same dev number etc yet they are in different PCI
> > > domains.
> > >
> > > Is this a device driver bug or feature?
> >
> > I hesitate to call it a device driver bug, because that was likely the
> > best decision Gerard could make at the time.
> >
> > However, I think the driver (only going by your description) would be
> > more correct to use a pointer to struct pci_dev. We have a token in the
> > kernel that is guaranteed 100% unique to any given PCI device: the
> > pointer to its struct pci_dev.
>
> The driver checks against PCI bus+dev+func in 2 situations:
>
> 1) To apply the boot order that user can set up in the controller NVRAMs.
> 2) To detect buggy double reporting of the same device by the kernel PCI
> code (this made lot of troubles at some time).
Thanks much for the clarification. Do you still battle buggy double reporting?
Has this been fixed? Is it a bug on some specific architecture?
> The great bug is to invent useless abstractions that don't match reality.
> Such brain masturbation leads to confusion (hence subtle bugs) and
> useless software bloatage (thus _real_ resource wastage).
Agreed. (A couple of my posts last night didn't make it through... appears that
us.ibm.com isn't set up entirely right for ENC)
> If we want to handle _real_ PCI bus domains, we just have to add a domain
> number to identify a _real_ PCI device. Anything that wants to hide such
> reality in some opaque data looks like brain masturbation to me.
Again also agreed. Now I'm REALLY anxious for 2.5 8-)
> Gérard.
Regards,
Tom
--
Tom Gall - PPC64 Maintainer "Where's the ka-boom? There was
Linux Technology Center supposed to be an earth
(w) tom_gall@vnet.ibm.com shattering ka-boom!"
(w) 507-253-4558 -- Marvin Martian
(h) tgall@rochcivictheatre.org
http://www.ibm.com/linux/ltc/projects/ppc
next prev parent reply other threads:[~2001-06-28 21:13 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 [this message]
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
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=3B3B9D83.F95D4496@vnet.ibm.com \
--to=tom_gall@vnet.ibm.com \
--cc=groudier@club-internet.fr \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.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