From owner-cvs-all  Wed May 23 15:42:17 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 036E937B422; Wed, 23 May 2001 15:42:14 -0700 (PDT)
	(envelope-from jhb@FreeBSD.org)
Received: (from jhb@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f4NMgDq53826;
	Wed, 23 May 2001 15:42:13 -0700 (PDT)
	(envelope-from jhb)
Message-Id: <200105232242.f4NMgDq53826@freefall.freebsd.org>
From: John Baldwin <jhb@FreeBSD.org>
Date: Wed, 23 May 2001 15:42:12 -0700 (PDT)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/vm vm_object.c
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

jhb         2001/05/23 15:42:12 PDT

  Modified files:
    sys/vm               vm_object.c 
  Log:
  - Assert that the vm lock is held for all of _vm_object_allocate().
  - Restore the previous order of setting up a new vm_object.  The previous
    had a small bug where we zero'd out the flags after we set the
    OBJ_ONEMAPPING flag.
  - Add several asserts of vm_mtx.
  - Assert Giant is held rather than locking and unlocking it in a few
    places.
  - Add in some #ifdef objlocks code to lock individual vm objects when
    vm objects each have their own lock someday.
  - Don't bother acquiring the allproc lock for a ddb command.  If DDB
    blocked on the lock, that would be worse than having an inconsistent
    allproc list.
  
  Revision  Changes    Path
  1.192     +49 -32    src/sys/vm/vm_object.c


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