From owner-cvs-all  Sat Feb 10 18:54:41 2001
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id E496B37B491; Sat, 10 Feb 2001 18:54:16 -0800 (PST)
Received: (from bmilekic@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f1B2sGD18146;
	Sat, 10 Feb 2001 18:54:16 -0800 (PST)
	(envelope-from bmilekic)
Message-Id: <200102110254.f1B2sGD18146@freefall.freebsd.org>
From: Bosko Milekic <bmilekic@FreeBSD.org>
Date: Sat, 10 Feb 2001 18:54:16 -0800 (PST)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/kern kern_mutex.c src/sys/sys mutex.h
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

bmilekic    2001/02/10 18:54:16 PST

  Modified files:
    sys/kern             kern_mutex.c 
    sys/sys              mutex.h 
  Log:
  - Place back STR string declarations for lock/unlock strings used for KTR_LOCK
    tracing in order to avoid duplication.
  - Insert some tracepoints back into the mutex acq/rel code, thus ensuring
    that we can trace all lock acq/rel's again.
  - All CURPROC != NULL checks are MPASS()es (under MUTEX_DEBUG) because they
    signify a serious mutex corruption.
  - Change up some KASSERT()s to MPASS()es, and vice-versa, depending on the
    type of problem we're debugging (INVARIANTS is used here to check that
    the API is being used properly whereas MUTEX_DEBUG is used to ensure that
    something general isn't happening that will have bad impact on mutex
    locks).
  
  Reminded by: jhb, jake, asmodai
  
  Revision  Changes    Path
  1.44      +20 -15    src/sys/kern/kern_mutex.c
  1.24      +36 -4     src/sys/sys/mutex.h



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