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

share/man/man9/vm_map_insert.9

@@ -25,7 +25,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd July 19, 2003
+.Dd January 11, 2013
 .Dt VM_MAP_INSERT 9
 .Os
 .Sh NAME
@@ -73,9 +73,6 @@ This function implicitly creates a new
 .Vt vm_map_entry
 by calling the internal function
 .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
 The
 .Fn vm_map_insert

share/man/man9/vm_map_stack.9

@@ -25,7 +25,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd July 19, 2003
+.Dd January 11, 2013
 .Dt VM_MAP_STACK 9
 .Os
 .Sh NAME
@@ -81,11 +81,11 @@ function calls
 to create its mappings.
 .Pp
 The
+.Fn vm_map_stack
+and
 .Fn vm_map_growstack
-function acquires the
-.Va Giant
-lock, and the process lock on
-.Fa p ,
+functions acquire the process lock on
+.Fa p
 for the duration of the call.
 .Sh RETURN VALUES
 The