From: Greg KH <greg@kroah.com>
To: "Cameron, Steve" <Steve.Cameron@hp.com>
Cc: linux-kernel@vger.kernel.org, "Mathiasen,
Torben" <Torben.Mathiasen@hp.com>,
"Ni, Michael" <Michael.Ni@hp.com>
Subject: Re: PCI hotplug question.
Date: Tue, 4 Mar 2003 22:15:20 -0800 [thread overview]
Message-ID: <20030305061520.GA26727@kroah.com> (raw)
In-Reply-To: <45B36A38D959B44CB032DA427A6E106404513370@cceexc18.americas.cpqcorp.net>
On Tue, Mar 04, 2003 at 05:10:16PM -0600, Cameron, Steve wrote:
>
> So, the question is this. For HBA drivers, block storage drivers in
> particular, are there plans to make hot-unplugging behave similarly to
> rmmod (checking that nobody has the device open before kicking
> the driver out and so on) or, is it the driver's duty to defend
> against incoming i/o's to devices which may be yanked out from
> underneath it whenever somebody presses the pushbutton?
I can't find my copy of the PCI Hotplug spec right now (and it's not
free for download anymore...), but I think that once a user presses the
latch button, the OS _has_ to power down that slot within a reasonable
amount of time. So there's no way that a driver could return an error
to the remove() callback and have a chance to still be around in a
moment or so. And some systems (ACPI controlled PCI Hotplug), we don't
have a choice, as the BIOS is about to do the powerdown anyway, and we
can't stop it.
So no, we can't rely on the same module count type mechanism that rmmod
can use, so the driver has to do everything it possibly can to shutdown
that device, and clean up after itself when remove() is called.
I'll try to find my copy of the spec to verify this, but it might take a
while to dig it up. Anyone else with access to it right now?
thanks,
greg k-h
next prev parent reply other threads:[~2003-03-05 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 23:10 PCI hotplug question Cameron, Steve
2003-03-05 6:15 ` Greg KH [this message]
2003-03-05 8:35 ` Russell King
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=20030305061520.GA26727@kroah.com \
--to=greg@kroah.com \
--cc=Michael.Ni@hp.com \
--cc=Steve.Cameron@hp.com \
--cc=Torben.Mathiasen@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox