src-test2/sys/vm, branch release/5.2.0_cvs

This commit was manufactured by cvs2svn to create tag

2004-01-10T05:53:29Z

'RELENG_5_2_0_RELEASE'. This commit was manufactured to restore the state of the 5.2-RELEASE image. Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

MFC revision 1.175

2003-12-11T20:30:15Z

Addendum to revision 1.174: In the case where vm_pager_allocate() is called to create a vnode-backed object, the vnode lock must be held by the caller. Approved by: re (scottl)

Fix a deadlock between vm_fault() and vm_mmap(): The expected lock ordering

2003-12-06T05:45:32Z

between vm_map and vnode locks is that vm_map locks are acquired first. In revision 1.150 mmap(2) was changed to pass a locked vnode into vm_mmap(). This creates a lock-order reversal when vm_mmap() calls one of the vm_map routines that acquires a vm_map lock. The solution implemented herein is to release the vnode lock in mmap() before calling vm_mmap() and reacquire this lock if necessary in vm_mmap(). Approved by: re (scottl) Reviewed by: jeff, kan, rwatson

Fix all users of mp_maxid to use the same semantics, namely:

2003-12-03T14:57:26Z

1) mp_maxid is a valid FreeBSD CPU ID in the range 0 .. MAXCPU - 1. 2) For all active CPUs in the system, PCPU_GET(cpuid) <= mp_maxid. Approved by: re (scottl) Tested on: i386, amd64, alpha

- Unbreak UP. mp_maxid is not defined on uni-processor machines, although

2003-11-30T22:18:14Z

I believe it and the other MP variables should be. For now, just define it here and wait for jhb to clean it up later. Approved by: re (rwatson)

- Replace the local maxcpu with mp_maxid. Previously, if mp_maxid

2003-11-30T08:04:01Z

was equal to MAXCPU, we would overrun the pcpu_mtx array because maxcpu was calculated incorrectly. - Add some more debugging code so that memory leaks at the time of uma_zdestroy() are more easily diagnosed. Approved by: re (rwatson)

- Avoid a lock-order reversal between Giant and a system map mutex that

2003-11-19T18:48:45Z

occurs when kmem_malloc() fails to allocate a sufficient number of vm pages. Specifically, we avoid the lock-order reversal by not grabbing Giant around pmap_remove() if the map is the kmem_map. Approved by: re (jhb) Reported by: Eugene

In vnode_pager_input_smlfs(), call VOP_STRATEGY instead of VOP_SPECSTRATEGY

2003-11-15T09:54:11Z

on non-VCHR vnodes. This fixes a panic when reading data from files on a filesystem with a small (less than a page) block size. PR: 59271 Reviewed by: alc

- Remove use of Giant from uma_zone_set_obj().

2003-11-14T17:49:07Z

- Remove long dead code.

2003-11-14T08:22:38Z