From owner-freebsd-arch Thu Nov 15 11:52:28 2001 Delivered-To: freebsd-arch@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C509137B421; Thu, 15 Nov 2001 11:52:21 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 2B99114C2E; Thu, 15 Nov 2001 20:52:20 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: John Baldwin Cc: freebsd-arch@FreeBSD.ORG, Peter Wemm , Bruce Evans , Greg Lehey , Alfred Perlstein , Matthew Dillon , Robert Watson Subject: Re: cur{thread/proc}, or not. References: From: Dag-Erling Smorgrav Date: 15 Nov 2001 20:52:19 +0100 In-Reply-To: Message-ID: Lines: 10 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin writes: > Err, no. curthread doesn't even have a lock. Look at sys/proc.h. There are > some fields we don't use any locks on, because we assume that only curthread > messes with its own copy, or some such. Hmm, then you need to lock the entire process, don't you? DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message