--OwLcNYc0lM97+oe1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 24, 2006 at 02:26:19PM +0530, Cherry G. Mathew wrote:
>=20
> On Apr 24, 2006, at 2:14 AM, Manuel Bouyer wrote:
>=20
> >I don't think we want howto as is here. We want a bitmask that can
> >express the various bits in howto, and more. For example, I'd like
> >to have shutdown hooks called 2 times: one from a valid kernel thread
> >context, so that the callee can tsleep, and one with interrupt blocked
> >(what we're currently doing). The call in kernel thread context would=20
> >be
> >usefull for raidframe, at last. I suspect other mid-layers may want it
> >too.

I think a bitmask would be good too.

> As far as I can tell, cpu_reboot() gets called from panic() and ddb,=20
> both of which
> can't be assumed to be within reliable thread context AFAIU. Therefore,=
=20
> would it
> be an acceptable implementation to call the shutdownhooks from
> within kern_xxx.c:sys_reboot() first, and then later within=20
> cpu_reboot() ( with
> flags indicating appropriate info) ?

Sounds good.

Take care,

Bill

--OwLcNYc0lM97+oe1
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFETQEXWz+3JHUci9cRAg1oAJ42KVF2lRzVvhjWB9p+0YsT3LRDAQCeMEAM
38to0pd9DXQHFhgnxcIdKf8=
=GtlH
-----END PGP SIGNATURE-----

--OwLcNYc0lM97+oe1--