Date: Tue, 2 Apr 2002 01:16:26 -0500 (EST) From: "Andrew R. Reiter" <arr@FreeBSD.org> To: smp@FreeBSD.org Subject: Where to initialize certain locks... Message-ID: <Pine.NEB.3.96L.1020402010619.18134D-100000@fledge.watson.org>
next in thread | raw e-mail | index | archive | help
I've been looking at some global values that are not associated with any one subsystem, but need a lock at some point in order to guarantee correct bheavior -- specifically, at the moment, the securelevel value. I do not right away see a clean place for the related lock to be initialized... Am I missing some SYSINIT() (or SYSINIT()s) that are meant for helping to initialize locks in this type of situation while still protecting/promoting correct order (to ensure we init prior to a lock attempt)? Or is that not a good path to go down? Cheers, Andrew -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1020402010619.18134D-100000>