The Giant lock is no longer used in the vm_map(9) part of the VM.
While here, document that the process lock is acquired in vm_map_stack, too. MFC after: 1 week
This commit is contained in:
parent
f404e02afd
commit
e86fef2a0b
@ -25,7 +25,7 @@
|
|||||||
.\"
|
.\"
|
||||||
.\" $FreeBSD$
|
.\" $FreeBSD$
|
||||||
.\"
|
.\"
|
||||||
.Dd July 19, 2003
|
.Dd January 11, 2013
|
||||||
.Dt VM_MAP_INSERT 9
|
.Dt VM_MAP_INSERT 9
|
||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
@ -73,9 +73,6 @@ This function implicitly creates a new
|
|||||||
.Vt vm_map_entry
|
.Vt vm_map_entry
|
||||||
by calling the internal function
|
by calling the internal function
|
||||||
.Fn vm_map_entry_create .
|
.Fn vm_map_entry_create .
|
||||||
This function may use the
|
|
||||||
.Va Giant
|
|
||||||
lock to ensure that only a single thread is present in the function.
|
|
||||||
.Sh RETURN VALUES
|
.Sh RETURN VALUES
|
||||||
The
|
The
|
||||||
.Fn vm_map_insert
|
.Fn vm_map_insert
|
||||||
|
@ -25,7 +25,7 @@
|
|||||||
.\"
|
.\"
|
||||||
.\" $FreeBSD$
|
.\" $FreeBSD$
|
||||||
.\"
|
.\"
|
||||||
.Dd July 19, 2003
|
.Dd January 11, 2013
|
||||||
.Dt VM_MAP_STACK 9
|
.Dt VM_MAP_STACK 9
|
||||||
.Os
|
.Os
|
||||||
.Sh NAME
|
.Sh NAME
|
||||||
@ -81,11 +81,11 @@ function calls
|
|||||||
to create its mappings.
|
to create its mappings.
|
||||||
.Pp
|
.Pp
|
||||||
The
|
The
|
||||||
|
.Fn vm_map_stack
|
||||||
|
and
|
||||||
.Fn vm_map_growstack
|
.Fn vm_map_growstack
|
||||||
function acquires the
|
functions acquire the process lock on
|
||||||
.Va Giant
|
.Fa p
|
||||||
lock, and the process lock on
|
|
||||||
.Fa p ,
|
|
||||||
for the duration of the call.
|
for the duration of the call.
|
||||||
.Sh RETURN VALUES
|
.Sh RETURN VALUES
|
||||||
The
|
The
|
||||||
|
Loading…
Reference in New Issue
Block a user