From owner-freebsd-arch  Thu May 25 10: 0:20 2000
Delivered-To: freebsd-arch@freebsd.org
Received: from berserker.bsdi.com (berserker.twistedbit.com [199.79.183.1])
	by hub.freebsd.org (Postfix) with ESMTP id A3FE737B52A
	for <arch@freebsd.org>; Thu, 25 May 2000 10:00:17 -0700 (PDT)
	(envelope-from cp@berserker.bsdi.com)
Received: from berserker.bsdi.com (cp@[127.0.0.1])
	by berserker.bsdi.com (8.9.3/8.9.3) with ESMTP id LAA25373;
	Thu, 25 May 2000 11:00:08 -0600 (MDT)
Message-Id: <200005251700.LAA25373@berserker.bsdi.com>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
	Terry Lambert <tlambert@primenet.com>, arch@freebsd.org
Subject: Re: Preemptive kernel on older X86 hardware 
From: Chuck Paterson <cp@bsdi.com>
Date: Thu, 25 May 2000 11:00:07 -0600
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

}
}    Lets use subroutines during development at least, it will make
}    things easier.  I don't think anyone can argue with that :-)
}

	Almost.) I certainly think that the actually locking
stuff can be in a function but we really want to wrap the
function in a macro so we can put tracing in. Being able
to look at a trace and see file and line numbers for mutex
locks and unlocks is invaluable.

Chuck



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message