Date: Mon, 11 Dec 2000 17:25:42 -0800 From: Jake Burkholder <jburkhol@home.com> To: Alfred Perlstein <bright@wintelcom.net> Cc: Jake Burkholder <jake@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, jake@io.yi.org Subject: Re: cvs commit: src/sys/conf files src/sys/sys mutex.h src/sys/kern kern_mutex.c src/sys/i386/i386 trap.c src/sys/ia64/ia64 trap.c src/sys/alpha/alpha trap.c Message-ID: <20001212012542.ADEDCBA7D@io.yi.org> In-Reply-To: Message from Alfred Perlstein <bright@wintelcom.net> of "Mon, 11 Dec 2000 17:20:48 PST." <20001211172048.R16205@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> * Jake Burkholder <jake@FreeBSD.org> [001211 17:14] wrote: > > jake 2000/12/11 17:14:33 PST > > > > Modified files: > > sys/conf files > > sys/sys mutex.h > > sys/kern kern_mutex.c > > sys/i386/i386 trap.c > > sys/ia64/ia64 trap.c > > sys/alpha/alpha trap.c > > Log: > > - Add code to detect if a system call returns with locks other than Giant > > held and panic if so (conditional on witness). > > Why not conditional on INVARIANTS? Couldn't this be easily tracked via > a counter in the proc struct? > > I'm trying to find a middle ground where the debug code doesn't make > development unbearable because of the slowdown. MUTEX_DEBUG and WITNESS > make compiling kernels (actually IO) too slow to be tolerated. > Because witness will print out the name(s) of the mutex(s) and the file and line number of where they were acquired. WITNESS isn't dependent on MUTEX_DEBUG anymore, I don't notice any performance problems running with just it enabled. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001212012542.ADEDCBA7D>