Remove nonsensical vm_map_{clear,set}_recursive() calls
from vm_map_pageable(). At the point they called, vm_map_pageable() holds a read (or shared) lock on the map. The purpose of vm_map_{clear,set}_recursive() is to disable/enable repeated write (or exclusive) lock requests by the same process.
This commit is contained in:
parent
e13b3c7870
commit
2b71c841f5
@ -1496,7 +1496,6 @@ vm_map_pageable(map, start, end, new_pageable)
|
||||
if (vm_map_pmap(map) == kernel_pmap) {
|
||||
vm_map_unlock(map); /* trust me ... */
|
||||
} else {
|
||||
vm_map_set_recursive(map);
|
||||
vm_map_lock_downgrade(map);
|
||||
}
|
||||
|
||||
@ -1526,8 +1525,6 @@ vm_map_pageable(map, start, end, new_pageable)
|
||||
|
||||
if (vm_map_pmap(map) == kernel_pmap) {
|
||||
vm_map_lock(map);
|
||||
} else {
|
||||
vm_map_clear_recursive(map);
|
||||
}
|
||||
if (rv) {
|
||||
vm_map_unlock(map);
|
||||
|
Loading…
Reference in New Issue
Block a user