From owner-freebsd-smp Mon Apr 1 22:16:35 2002 Delivered-To: freebsd-smp@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9911937B41C for ; Mon, 1 Apr 2002 22:16:31 -0800 (PST) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g326GRl21864 for ; Tue, 2 Apr 2002 01:16:27 -0500 (EST) (envelope-from arr@FreeBSD.org) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Tue, 2 Apr 2002 01:16:26 -0500 (EST) From: "Andrew R. Reiter" X-Sender: arr@fledge.watson.org To: smp@FreeBSD.org Subject: Where to initialize certain locks... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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