From owner-cvs-src@FreeBSD.ORG  Wed Jul  2 09:14:09 2003
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id BF18337B401; Wed,  2 Jul 2003 09:14:09 -0700 (PDT)
Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 729B043FBD; Wed,  2 Jul 2003 09:14:09 -0700 (PDT)
	(envelope-from jhb@FreeBSD.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.12.6/8.12.6) with ESMTP id h62GE90U033257;
	Wed, 2 Jul 2003 09:14:09 -0700 (PDT)
	(envelope-from jhb@repoman.freebsd.org)
Received: (from jhb@localhost)
	by repoman.freebsd.org (8.12.6/8.12.6/Submit) id h62GE9Ud033253;
	Wed, 2 Jul 2003 09:14:09 -0700 (PDT)
Message-Id: <200307021614.h62GE9Ud033253@repoman.freebsd.org>
From: John Baldwin <jhb@FreeBSD.org>
Date: Wed, 2 Jul 2003 09:14:09 -0700 (PDT)
To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org,
	cvs-all@FreeBSD.org
X-FreeBSD-CVS-Branch: HEAD
Subject: cvs commit: src/sys/kern kern_mutex.c
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jul 2003 16:14:10 -0000

jhb         2003/07/02 09:14:09 PDT

  FreeBSD src repository

  Modified files:
    sys/kern             kern_mutex.c 
  Log:
  - Add comments about the maintenance of the per-thread list of contested
    locks held by each thread.
  - Fix a bug in the original BSD/OS code where a contested lock was not
    properly handed off from the old thread to the new thread when a
    contested lock with more than one blocked thread was transferred from
    one thread to another.
  - Don't use an atomic operation to write the MTX_CONTESTED value to
    mtx_lock in the aforementioned special case.  The memory barriers and
    exclusion provided by sched_lock are sufficient.
  
  Spotted by:     alc (2)
  
  Revision  Changes    Path
  1.129     +9 -4      src/sys/kern/kern_mutex.c