Subject: Re: [PATCH] call drv->shutdown at rmmod
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Patrick Mochel <mochel@osdl.org>, Greg KH <greg@kroah.com>,
       linux-kernel mailing list <linux-kernel@vger.kernel.org>
In-Reply-To: <m1oeyrx7mo.fsf@frodo.biederman.org>
References: <Pine.LNX.4.33.0308140929180.916-100000@localhost.localdomain>
	 <1060937467.13316.39.camel@gaston>  <m1oeyrx7mo.fsf@frodo.biederman.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1060963263.643.48.camel@gaston>
Mime-Version: 1.0
Date: 15 Aug 2003 18:01:03 +0200
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1088
Lines: 25


> Even if kexec is not brought into the picture the devices need to be quiesed on
> reboot.  On x86 and probably other architectures there are 2 ways a reboot can go.
> 1) The firmware when it regains control toggles the motherboard reset
>    line resetting all of the devices, so nothing we do really makes a difference.
> 2) The firmware when it regains control tweaks a few things and
>    pretends it was never out of control, and restarts the boot
>    process.
> 
> When the firmware does not toggle the motherboard reset line during a
> reboot the firmware case is exactly equivalent to the kexec one.
> 
> So shutdown needs to quiese things.

Yup, my point was mostly to say that quiescing for shutdown and putting
in low power state are 2 different things, and that the "shutdown" name
for the callback is a bit misleading...

Ben.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/