From owner-cvs-all Sun Feb 25 5:33:54 2001 Delivered-To: cvs-all@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 3311037B491; Sun, 25 Feb 2001 05:33:49 -0800 (PST) (envelope-from bp@butya.kz) Received: by relay.butya.kz (Postfix, from userid 1000) id B479B28C8F; Sun, 25 Feb 2001 19:33:42 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 20DFC28C87; Sun, 25 Feb 2001 19:33:42 +0600 (ALMT) Date: Sun, 25 Feb 2001 19:33:41 +0600 (ALMT) From: Boris Popov To: John Baldwin Cc: Bruce Evans , cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/conf NOTES src/sys/conf options In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Feb 2001, John Baldwin wrote: > > Now removing INVARIANT_SUPPORT is back on my todo list :-]. It enables > > a whole 28 lines of code (the _mtx_assert() function). It seems to > > I think Eivind's point was that you may want to just have support for > invariants in your kernel and then build a kernel module that you are debugging > with invariants. For example, if I wanted to debug a device driver that used > mutexes, I might build it with INVARIANTS so that the mtx_assert()'s do > something useful. However, I may not wish to turn on INVARIANTS in my base > kernel for some reason, and I can get by by building a kernel with just > INVARIANT_SUPPORT compiled in.. And this works until structures are the same for both cases. The most notable breakage was a kernel compiled with INVARIANTS and a KLD compiled without them. Any attempt to work with zone allocator leads to mysterious panics. Now it seems to be fixed (thanks DES :) -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message