Alan Cox e50346b5e0 The so-called "optimized copy-on-write fault" case should not require ...

the vm map lock.  What's really needed is vm object locking, which
is (for the moment) provided Giant.

Reviewed by:	tegge

2003-06-20 04:20:36 +00:00

..

default_pager.c

…

device_pager.c

…

phys_pager.c

…

pmap.h

…

swap_pager.c

This file was ignored by CVS in my last commit for some reason:

2003-06-16 09:31:15 +00:00

swap_pager.h

…

uma_core.c

…

uma_dbg.c

…

uma_dbg.h

…

uma_int.h

…

uma.h

…

vm_contig.c

…

vm_extern.h

…

vm_fault.c

The so-called "optimized copy-on-write fault" case should not require

2003-06-20 04:20:36 +00:00

vm_glue.c

…

vm_init.c

…

vm_kern.c

…

vm_kern.h

…

vm_map.c

…

vm_map.h

Remove an unnecessary forward declaration.

2003-06-15 07:28:33 +00:00

vm_meter.c

…

vm_mmap.c

…

vm_object.c

…

vm_object.h

…

vm_page.c

Assert that the vm object is locked in vm_page_try_to_free().

2003-06-19 01:50:14 +00:00

vm_page.h

…

vm_pageout.c

…

vm_pageout.h

…

vm_pageq.c

…

vm_pager.c

…

vm_pager.h

…

vm_param.h

…

vm_swap.c

Add the same KASSERT to all VOP_STRATEGY and VOP_SPECSTRATEGY implementations

2003-06-15 18:53:00 +00:00

vm_unix.c

…

vm_zeroidle.c

…

vm.h

…

vnode_pager.c

Lock the vm object when freeing a vm page.

2003-06-18 04:27:18 +00:00

vnode_pager.h

…