Updates to capability and l4_capability_control

docs/man/man7/capability.7

@@ -3,6 +3,11 @@
 .nf
 .BR "Capability" " - Overview of Capabilities in Codezero"
 
+.SH SYNOPSIS
+.nf
+.B #include <l4/api/capability.h>
+.B #include <l4/generic/cap-types.h>
+
 .SH DESCRIPTION
 A capability is a unique representation of security qualifiers on a particular resource.
 Each thread, address space and container is associated with its own capability list represented by the below structure.

docs/man/man7/l4_capability_control.7

@@ -1,7 +1,7 @@
 .TH L4_CAPABILITY_CONTROL 7 2009-11-07 "Codezero" "Codezero Programmer's Manual"
 .SH NAME
 .nf
-.BR "l4_capability_control" "- Set/Get Various capabilities of thread"
+.BR "l4_capability_control" " - Capability inspection and manipulation"
 
 .SH SYNOPSIS
 .nf
@@ -11,17 +11,24 @@
 .BI "int l4_capability_control (unsigned int " "req" ", unsigned int " "flags",
 .BI "                           l4id_t " "capid" ", l4id_t " "tid" ", void " "*buf" ");"
 .SH DESCRIPTION
-.BR l4_capability_control() " -"
+.BR l4_capability_control() " - "
-Sets various capabilities of a thread, capabilities are read/modified always with respect to current task/thread, current address space or current container. The thread calling this system call must posses a capability to do capability. It returns
+enables a thread to read and manipulate the list of capabilities that it possesses. Capabilities may be shared, granted to other threads, or they may be replicated, destroyed, reduced in privileges or split into parts, effectively enabling a dynamically configurable resource management architecture. The thread calling this system call must possess relevant capabilities as any operation done by this call are also subject to capability checking.
-.B ENOCAP
+.TP
-if the capabilities specified by 
+.fi
 .I req
-and
+denotes the type of request. See below for a full list.
+.TP
+.fi
 .I flags
-are not valid capabilities for current thread. 
+denotes additional flags for the given request. See below for a list of flags.
+.TP
+.fi
 
-.I req
+.I buf
-is type of requtest and can take one of these values
+almost always contains a capability structure that describes the request with regard to given
+.IR "req"
+and
+.IR "flags."
 .TP
 .BR CAP_CONTROL_NCAPS
 Get capability count, sum of private capabilities, address space capabilities and container capabilities.
@@ -64,7 +71,7 @@ Capabilities are split by diff'ing resources possessed between capabilities.
 .I flags
 may be one of
 .B CAP_SPLIT_SIZE
-or
+,
 .B CAP_SPLIT_ACCESS
 or
 .B CAP_SPLIT_RANGE.
@@ -95,10 +102,12 @@ Returns 0 on success, and negetive error value on failure. See below for errors
 .SH ERRORS
 .TP
 .B EINVAL
-when a capability struct is passed, but it has some invalid fields.
+when a capability struct is passed in
+.IR "buf"
+but has some invalid fields.
 .TP
 .B ENOCAP
-when capabilities doesn't match or doesn't exists.
+when capabilities required don't exist or do not have sufficient privileges.
 
 .SH SEE ALSO
 .BR "capability"(7)