From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Khachaturov, Vassilii" <Vassilii.Khachaturov@comverse.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: Changes for PCI
Date: Thu, 28 Jun 2001 19:27:10 -0400 [thread overview]
Message-ID: <3B3BBD4E.BDDF63DA@mandrakesoft.com> (raw)
In-Reply-To: <6B1DF6EEBA51D31182F200902740436802678FB5@mail-in.comverse-in.com>
"Khachaturov, Vassilii" wrote:
>
> On Wed, 27 Jun 2001, Jeff Garzik wrote:
>
> > 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.
>
> Is it? With a hotplug device removed and another one added,
> isn't there a slight chance that the pci_dev pointer to the new device
> will get allocated in place of the old one?
If you want to get pedantic, yes ;-) The pci_dev pointer is unique for
the lifetime of the PCI device, which works just as well in the example
used in the thread.
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-06-28 23:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 23:08 RFC: Changes for PCI Khachaturov, Vassilii
2001-06-28 23:27 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-27 22:06 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
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
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=3B3BBD4E.BDDF63DA@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Vassilii.Khachaturov@comverse.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.