All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Gall <tom_gall@vnet.ibm.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: Changes for PCI
Date: Wed, 27 Jun 2001 13:24:25 -0500	[thread overview]
Message-ID: <3B3A24D9.5013B835@vnet.ibm.com> (raw)
In-Reply-To: <3B3A58FC.2728DAFF@vnet.ibm.com> <3B3A5B00.9FF387C9@mandrakesoft.com> <3B3A64CD.28B72A2A@vnet.ibm.com> <3B3A6D80.E82A2BA6@mandrakesoft.com>



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.

I don't doubt it. I wouldn't doubt I've been guilty of simliar things in my past...


> 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.

Sound good.

> > > Changing the meaning of dev->bus->number globally seems pointless.  If
> > > you are going to do that, just do it the right way and introduce another
> > > struct member, pci_domain or somesuch.
>
> Sorry, not pci_domain, just system bus number, for any bus, like we
> talked about in the previous discussion.

Yes agreed. However do you think it's possible for the additional of such a value now
in 2.4.x series? Alan? Linus?

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



  reply	other threads:[~2001-06-28  2:43 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 [this message]
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
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=3B3A24D9.5013B835@vnet.ibm.com \
    --to=tom_gall@vnet.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.