From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: How to find hotplug slot of PCI dev?
Date: Thu, 30 Jun 2005 00:36:43 +0000 [thread overview]
Message-ID: <20050630003643.GA20349@kroah.com> (raw)
In-Reply-To: <20050629230019.GP28499@austin.ibm.com>
On Wed, Jun 29, 2005 at 07:14:43PM -0500, Linas Vepstas wrote:
> Yes, but a PCI error will take out *all* of the functions plugged into a
> slot. It might even take out multiple slots, if the error occured on a
> cable connecting the CPU to the drawer with the pci cards in it.
Then all of those pci_dev will get notified, right? And if they all
start to try to power cycle the same card, bad things will probably
happen, right?
Again, refer to the PCI Hotplug spec for the fact that I do not think
this is allowable behaviour.
> Don't know anything about USB, but I assume that there is such a thing
> as a USB controller reset, and that will take out the entire chain
> until the reset completes.
There can be multiple USB controllers on a single PCI card, that are
independant of each other (much like network controllers can be.)
And USB 2.0 controllers have a built-in pci bridge with a USB 1.1
controller attached to it. So it can be quite deep just at the PCI
layer.
> Its not all that much meaner than asserting the #RST line. The point
> was that toggling the power was an effective way of dealing with device
> for which the device drivers don't support PCI error recovery. But now
> that I've got 5 drivers that do handle recovery, and some more in the
> works, maybe in fact I don't much need hotplug-based recovery any more,
> and I could just let that drop.
Sounds like a wise thing :)
thanks,
greg k-h
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-06-30 0:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 23:00 How to find hotplug slot of PCI dev? Linas Vepstas
2005-06-29 23:26 ` Greg KH
2005-06-30 0:14 ` Linas Vepstas
2005-06-30 0:36 ` Greg KH [this message]
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=20050630003643.GA20349@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).