sambuc/codezero
1
0
Fork 0
mirror of https://github.com/drasko/codezero.git synced 2026-03-27 14:29:03 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updates to kip, capability and cap control man pages.

Browse Source
This commit is contained in:
Bahadir Balban
2009-12-04 15:44:16 +02:00
parent 2908c40816
commit 825ee3f476
3 changed files with 180 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/man/man7/capability.7
View File

@@ -44,18 +44,22 @@ The capability structure is defined as follows:
.fi
.I capid
denotes the unique capability ID.
.TP
.fi
.I resid
denotes the unique ID of targeted resource. The smallest resource targetable by a capability is a thread. There are also collections of targetable resources such as an address space or a container. An address space target resource implies all threads inside that address space, and a container target resource implies all threads inside that container. Quantitative capabilities such as typed memory pools do not possess a target, and therefore have an invalid resource ID.
.TP
.fi
.I owner
denotes the unique ID of the one and only capability owner. This is always a thread ID. The ownership of a capability determines who has the right to practise the capability modification privileges available over the capability, such as sharing, granting, spliting, reducing or destruction of the capability.
.TP
.fi
.I type
field contains the capability type or targeted resource type. The capability type determines the generic operations that the capability describes. For example a capability describing a system call would likely have a type name that resembles the name of that system call. See below for the list of valid capability types. The resource type denotes the type of targeted resources. In case this is a thread or a collection of threads, the type may be one of thread, address space, or container. Quantitative resources also have different types, describing the resource. Since quantitative resources such as memory pools, or memory regions are not associated with a target id, the types have no meaning for the resid field for these capabilities. See below for the full list of valid resource types.
.TP
.fi
.I access