From owner-freebsd-current Thu Apr 25 10:59:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 751F537B416; Thu, 25 Apr 2002 10:59:42 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 8E1995309; Thu, 25 Apr 2002 19:59:38 +0200 (CEST) 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: Hiten Pandya , current@FreeBSD.org Subject: Re: Spin lock (?) problems with MUTEX_PROFILING References: From: Dag-Erling Smorgrav Date: 25 Apr 2002 19:59:37 +0200 In-Reply-To: Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@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: > This means WITNESS is broken with MUTEX_PROFIING (I guess they were > never tested together without WITNESS_SKIPSPIN). WITNESS makes my box about as useful as a heap of bricks, so no, MUTEX_PROFILING was never tested with WITNESS. > The fix is for the > MUTEX_PROFILING folks to add the spin lock into the spin lock order > list in the proper location. Junior kernel hacker task. Note that it's always a leaf lock - no lock is ever acquired while the profiling lock is held. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message