From d5cf4c5275f6e664075d1972274e99a697bd6823 Mon Sep 17 00:00:00 2001 From: jhb Date: Tue, 22 Apr 2003 20:01:56 +0000 Subject: Prefer the proc lock to sched_lock when testing PS_INMEM now that it is safe to do so. --- sys/vm/vm_fault.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'sys/vm/vm_fault.c') diff --git a/sys/vm/vm_fault.c b/sys/vm/vm_fault.c index d2d7372..d8f2409 100644 --- a/sys/vm/vm_fault.c +++ b/sys/vm/vm_fault.c @@ -917,15 +917,16 @@ readrest: } vm_page_wakeup(fs.m); vm_page_unlock_queues(); - mtx_lock_spin(&sched_lock); - if (curproc && (curproc->p_sflag & PS_INMEM) && curproc->p_stats) { + + PROC_LOCK(curproc); + if ((curproc->p_sflag & PS_INMEM) && curproc->p_stats) { if (hardfault) { curproc->p_stats->p_ru.ru_majflt++; } else { curproc->p_stats->p_ru.ru_minflt++; } } - mtx_unlock_spin(&sched_lock); + PROC_UNLOCK(curproc); /* * Unlock everything, and return -- cgit v1.1