Re: [PATCH] call drv->shutdown at rmmod
From: Benjamin Herrenschmidt (benh_at_kernel.crashing.org)
Date: 08/15/03
- Previous message: David Woodhouse: "Re: Reiser4 status: benchmarked vs. V3 (and ext3)"
- Maybe in reply to: Eric W. Biederman: "[PATCH] call drv->shutdown at rmmod"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: "Eric W. Biederman" <ebiederm@xmission.com> Date: 15 Aug 2003 18:01:03 +0200
> 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/
- Previous message: David Woodhouse: "Re: Reiser4 status: benchmarked vs. V3 (and ext3)"
- Maybe in reply to: Eric W. Biederman: "[PATCH] call drv->shutdown at rmmod"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]