From owner-freebsd-current Thu Apr 25 11:20:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.speakeasy.net (mail13.speakeasy.net [216.254.0.213]) by hub.freebsd.org (Postfix) with ESMTP id 6637E37B405 for ; Thu, 25 Apr 2002 11:20:32 -0700 (PDT) Received: (qmail 5162 invoked from network); 25 Apr 2002 18:20:30 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail13.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 25 Apr 2002 18:20:30 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g3PIKZv11346; Thu, 25 Apr 2002 14:20:35 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 25 Apr 2002 14:19:38 -0400 (EDT) From: John Baldwin To: Dag-Erling Smorgrav Subject: Re: Spin lock (?) problems with MUTEX_PROFILING Cc: current@FreeBSD.org, Hiten Pandya 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 On 25-Apr-2002 Dag-Erling Smorgrav wrote: > 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. Since WITNESS makes sure you use locks properly, you should use it when you are making changes to the locking subsystem. Esp. if you are messing with spin locks. It may be slow but it's still usable for doing a bootup. Getting into single user mode with profiling on would have highlighted this problem. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message