From: Matthew Wilcox <willy@debian.org>
To: Greg KH <greg@kroah.com>
Cc: Matthew Wilcox <willy@debian.org>,
Linus Torvalds <torvalds@osdl.org>,
"David S. Miller" <davem@redhat.com>,
Jeff Garzik <jgarzik@pobox.com>,
linux-pci@atrey.karlin.mff.cuni.cz, netdev@oss.sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pci_get_slot()
Date: Wed, 15 Oct 2003 19:50:53 +0100 [thread overview]
Message-ID: <20031015185053.GH16535@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20031015184104.GA22373@kroah.com>
On Wed, Oct 15, 2003 at 11:41:04AM -0700, Greg KH wrote:
> The check of:
> if (dev->bus->number == bus && dev->devfn == devfn)
> in pci_find_slot() doesn't check for the domain?
No, it would also need to check pci_domain_nr(dev->bus) .. and it doesn't
have anything to check it against as that information isn't passed into
the function.
> Anyway, is there any other way you can fix this in the tg3 driver only
> for right now? I agree adding the pci function is "cleaner", but a bit
> late for right now.
The only real way to do it is to inline pci_get_slot() into tg3. Since I
also have a need for it in sym2, that doesn't seem like a sensible idea.
It would also be racy since it wouldn't take the pci_bus_lock.
> How does this differ from pci_find_slot()? (becides the pci_dev_get()
> call)? pci_find_slot() asks for the bus number, which can be determined
> from the pci_bus structure, right?
The pci_bus knows which domain it's in. We don't have to check it since
we only walk its children.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-10-15 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 18:32 [PATCH] pci_get_slot() Matthew Wilcox
2003-10-15 18:41 ` Greg KH
2003-10-15 18:50 ` Matthew Wilcox [this message]
2003-10-15 19:34 ` Greg KH
2003-10-15 19:55 ` Jeff Garzik
2003-10-15 19:13 ` Linus Torvalds
2003-12-18 0:24 ` Greg KH
2003-12-18 20:00 ` Matthew Wilcox
2004-01-29 22:46 ` Greg KH
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=20031015185053.GH16535@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=davem@redhat.com \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=netdev@oss.sgi.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).