summaryrefslogtreecommitdiffstats
path: root/sys/vm/vm_fault.c
Commit message (Expand)AuthorAgeFilesLines
* Eliminate the acquisition and release of the page queues lock around a callalc2006-08-061-4/+2
* Retire debug.mpsafevm. None of the architectures supported in CVS requirealc2006-07-211-7/+1
* Remove mpte optimization from pmap_enter_quick().ups2006-06-151-4/+2
* Simplify the implementation of vm_fault_additional_pages() based upon thealc2006-05-131-12/+5
* Remove leading __ from __(inline|const|signed|volatile). They areimp2006-03-081-2/+2
* Adjust old comment (present in rev 1.1) to match changes in rev 1.82.tegge2006-02-021-1/+1
* Use the new macros abstracting the page coloring/queues implementation.alc2006-01-271-2/+2
* MI changes:netchild2005-12-311-2/+3
* Don't access fs->first_object after dropping reference to it.tegge2005-12-201-1/+3
* Remove unneeded calls to pmap_remove_all(). The given page is not mapped.alc2005-12-111-1/+0
* Eliminate an incorrect cast.alc2005-09-071-1/+1
* Pass a value of type vm_prot_t to pmap_enter_quick() so that it determinealc2005-09-031-1/+2
* Convert a remaining !fs.map->system_map tojhb2005-07-141-1/+1
* The final test in unlock_and_deallocate() to determine if GIANT needs to begrehan2005-05-121-1/+1
* - Add a new object flag "OBJ_NEEDSGIANT". We set this flag if thejeff2005-05-031-4/+9
* - Remove GIANT_REQUIRED where giant is no longer required.jeff2005-01-241-2/+6
* /* -> /*- for license, minor formatting changesimp2005-01-071-1/+1
* Continue the transition from synchronizing access to the page's PG_BUSYalc2004-12-241-11/+29
* Modify pmap_enter_quick() so that it expects the page queues to be lockedalc2004-12-231-4/+3
* In the common case, pmap_enter_quick() completes without sleeping.alc2004-12-151-8/+2
* Remove unnecessary check for curthread == NULL.alc2004-10-171-1/+1
* System maps are prohibited from mapping vnode-backed objects. Takealc2004-09-111-8/+8
* Push Giant deep into vm_forkproc(), acquiring it only if the process hasalc2004-09-031-0/+4
* In vm_fault_unwire() eliminate the acquisition and release of Giant in thealc2004-09-011-4/+0
* In the previous revision, I failed to condition an early release of Giantalc2004-08-221-1/+2
* Further reduce the use of Giant by vm_fault(): Giant is held only whenalc2004-08-211-4/+3
* - Introduce and use a new tunable "debug.mpsafevm". At present, settingalc2004-08-161-7/+11
* The vm map lock is needed in vm_fault() after the page has been found,tegge2004-08-121-51/+37
* Make two changes to vm_fault().alc2004-08-091-16/+7
* Make two changes to vm_fault().alc2004-08-091-11/+6
* To date, unwiring a fictitious page has produced a panic. The reasonalc2004-05-221-11/+10
* Make vm_page's PG_ZERO flag immutable between the time of the page'salc2004-05-061-1/+0
* - Make the acquisition of Giant in vm_fault_unwire() conditional on thealc2004-03-101-2/+4
* Correct a long-standing race condition in vm_fault() that could result in aalc2004-02-151-3/+1
* - Locking for the per-process resource limits structure has eliminatedalc2004-02-051-2/+0
* - Reduce Giant's scope in vm_fault().alc2003-12-261-14/+10
* NFC: Update stale comments.mini2003-11-101-1/+1
* - vm_fault_copy_entry() should not assume that the source object containsalc2003-10-151-5/+19
* Lock the destination object in vm_fault_copy_entry().alc2003-10-081-2/+7
* Retire vm_page_copy(). Its reason for being ended when peter@ modifiedalc2003-10-081-2/+4
* Synchronize access to a vm page's valid field using the containingalc2003-10-041-4/+8
* Migrate pmap_prefault() into the machine-independent virtual memory layer.alc2003-10-031-1/+91
* Add vm object locking to vnode_pager_lock(). (This triggers the movementalc2003-09-181-1/+1
* To implement the sequential access optimization, vm_fault() may need toalc2003-08-231-8/+10
* Maintain a lock on the vm object of interest throughout vm_fault(),alc2003-06-221-10/+9
* As vm_fault() descends the chain of backing objects, set paging-in-alc2003-06-221-8/+8
* Make some style and white-space changes to the copy-on-write path throughalc2003-06-221-10/+5
* Lock one of the vm objects involved in an optimized copy-on-write fault.alc2003-06-211-2/+5
* The so-called "optimized copy-on-write fault" case should not requirealc2003-06-201-9/+2
* Fix a vm object reference leak in the page-based copy-on-write mechanismalc2003-06-191-1/+1
OpenPOWER on IntegriCloud