Date: Tue, 02 Apr 2002 00:36:35 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: "Andrew R. Reiter" <arr@FreeBSD.org> Cc: smp@FreeBSD.org Subject: Re: Where to initialize certain locks... Message-ID: <3CA96D93.3DAE8C58@mindspring.com> References: <Pine.NEB.3.96L.1020402010619.18134D-100000@fledge.watson.org>
index | next in thread | previous in thread | raw e-mail
"Andrew R. Reiter" wrote: > > 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? Initialized to what non-default setting? Initializing a lock as locked is a bad idea. Initializing it as unlocked is, well, automatic. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the messagehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CA96D93.3DAE8C58>