Re: Where to initialize certain locks...

On 02-Apr-2002 Terry Lambert wrote:
> "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.

No it's not.

-- 

John Baldwin <[e-mail]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [e-mail]
with "unsubscribe freebsd-smp" in the body of the message