summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJustus Winter <justus@gnupg.org>2016-02-28 16:35:42 +0100
committerJustus Winter <justus@gnupg.org>2016-02-28 17:34:08 +0100
commit48b69fb81c590bee4ace4ed98064771db9ec31ca (patch)
tree9bb37f8bae4e857b7b8e238f625cbbe876495b17
parent55b55f51325893542005763a7e50adcf60548112 (diff)
doc: clarify memory object initialization
* doc/mach.texi: Mention another way how a memory manager can signal that an object is ready.
-rw-r--r--doc/mach.texi5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/mach.texi b/doc/mach.texi
index 6fc79f70..0aeed766 100644
--- a/doc/mach.texi
+++ b/doc/mach.texi
@@ -3526,8 +3526,9 @@ each will perform a @code{memory_object_init} call with new request and
name ports. The virtual page size that is used by the calling kernel is
included for planning purposes.
-When the memory manager is prepared to accept requests for data for this
-object, it must call @code{memory_object_ready} with the attribute.
+When the memory manager is prepared to accept requests for data for
+this object, it must call @code{memory_object_ready}, or set the ready
+flag using @code{memory_object_set_attributes}.
Otherwise the kernel will not process requests on this object. To
reject all mappings of this object, the memory manager may use
@code{memory_object_destroy}.