From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: unclean yanking out of device?
Date: Thu, 15 Jan 2004 00:36:29 +0000 [thread overview]
Message-ID: <4005E08D.6010002@pacbell.net> (raw)
In-Reply-To: <20040114160002.G57254@forte.austin.ibm.com>
>>>That pci controller needs to tell the OS that it is going to shut down
>>>that pci slot. Otherwise that pci controller violates the PCI spec.
>>
>>I was only half-joking about the cosmic ray. The cosmic ray violated
>>the PCI spec. boo hoo. Now what? Tell it to go back to the supernova
>>it came from?
>
>
> No, tell the driver that it is going to be shut down. The driver will
> do so, and then you can safely yank it out. That's what all pci hotplug
> controller drivers do, why be different?
Actually there's a good argument that every PCI driver for hardware that
can be packaged onto CardBus _should_ handle those "unclean" shutdown
modes ... and as Linus has observed, it's awfully convenient that most
such cases also cause reads from those devices to return all-ones!
The electrical details are of course a different issue. Cardbus and
the various other kinds of PCI hotplug have different answers, so
there's no universal guarantee that drivers will get notified first.
- Dave
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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
next prev parent reply other threads:[~2004-01-15 0:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 22:00 unclean yanking out of device? linas
2004-01-14 22:15 ` Måns Rullgård
2004-01-14 22:19 ` Greg KH
2004-01-14 23:08 ` linas
2004-01-14 23:24 ` Greg KH
2004-01-14 23:49 ` Paul Ionescu
2004-01-14 23:57 ` linas
2004-01-15 0:19 ` Oliver Neukum
2004-01-15 0:19 ` Greg KH
2004-01-15 0:34 ` Greg KH
2004-01-15 0:36 ` David Brownell [this message]
2004-01-15 1:16 ` linas
2004-01-15 1:20 ` linas
2004-01-15 1:33 ` Greg KH
2004-01-15 1:35 ` Greg KH
2004-01-15 1:57 ` linas
2004-01-15 17:17 ` Richard Troth
2004-01-15 18:38 ` linas
2004-01-15 21:22 ` David Hinds
2004-01-24 0:38 ` 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=4005E08D.6010002@pacbell.net \
--to=david-b@pacbell.net \
--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 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.