From: "Randy.Dunlap" <rddunlap@osdl.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: mochel@osdl.org, greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] call drv->shutdown at rmmod
Date: Thu, 14 Aug 2003 09:47:33 -0700 [thread overview]
Message-ID: <20030814094733.024675ba.rddunlap@osdl.org> (raw)
In-Reply-To: <m13cg4yzlk.fsf@frodo.biederman.org>
On 14 Aug 2003 10:26:47 -0600 ebiederm@xmission.com (Eric W. Biederman) wrote:
| Patrick Mochel <mochel@osdl.org> writes:
|
| > > At the kexec BOF at OSDL there was some discussion on calling the
| > > device shutdown method at module remove time, in addition to calling
| > > it during reboot. The driver was the observation that the primary
| > > source of problems in booting linux from linux are drivers with bad
| > > or missing drv->shutdown() routines. The hope is this will increase
| > > the testing so people can get it right and kexec can become more
| > > useful. In addition to making normal reboots more reliable.
| > >
| > > The following patch is an implementation of that idea it calls drv->shutdown()
| >
| > > before calling drv->remove(). If drv->shutdown() is implemented.
| >
| > I like the idea behind the patch, but we shouldn't be calling it
| > unconditionally. We're bound to run into some suprises that could really
| > kill us this late in the 2.6 game.
| >
| > I do think it should go in, as long as there is a flag telling the core
| > whether or not to call shutdown for that particular device. I think it
| > could also be extended to include a power state, so the core could suspend
| > the device before removing the module.
|
| Assuming the device driver can get a device out of the suspend state
| when the module is loaded. This has been one of the biggest problem areas
| with the e100 driver. It's init code cannot bring the device out of a low
| power state.
|
| > The default would always be 'Do Nothing', but with a per-device sysfs
| > file, a developer/user/gui app could be used to set the policy from user
| > space.
|
| Possibly. But this is getting complicated. And while I do support things
| being complicated enough to handle the problem this part of the API feels
| like it is excessively complicated. Which is why I was trying to simply
| it by always calling shutdown on a device before we remove it.
Can it just be a (kernel hacking/debug) CONFIG_DRIVER_SHUTDOWN build
option?
--
~Randy
prev parent reply other threads:[~2003-08-14 16:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 7:06 [PATCH] call drv->shutdown at rmmod Eric W. Biederman
2003-08-14 7:54 ` Christoph Hellwig
2003-08-14 8:06 ` Russell King
2003-08-14 15:50 ` Eric W. Biederman
2003-08-14 16:07 ` Russell King
2003-08-14 17:26 ` Eric W. Biederman
2003-08-17 22:26 ` [PATCH] don't call device_shutdown on halt Eric W. Biederman
2003-08-14 16:40 ` [PATCH] call drv->shutdown at rmmod Russell King
2003-08-14 16:02 ` Patrick Mochel
2003-08-14 16:26 ` Eric W. Biederman
2003-08-14 16:41 ` Patrick Mochel
2003-08-14 17:41 ` Eric W. Biederman
2003-08-15 8:51 ` Benjamin Herrenschmidt
2003-08-15 15:28 ` Eric W. Biederman
2003-08-15 16:01 ` Benjamin Herrenschmidt
2003-08-15 16:30 ` Patrick Mochel
2003-08-14 16:47 ` Randy.Dunlap [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=20030814094733.024675ba.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@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).