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

Updates to l4_capability_control

Browse Source
This commit is contained in:
Bahadir Balban
2009-12-02 19:06:38 +02:00
parent 2c93de65bf
commit 8b0aab976a
3 changed files with 35 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/man/man7/l4_mutex_control.7
View File

@@ -27,20 +27,18 @@ Typically the lock is placed on a shared memory segment.
.ti 16
The virtual address can be different on different address spaces referring to the same lock.
Mutexes are locked and unlocked with no system call assistance if there is no lock contention.
If a lock contention occurs, lock holder and lock contender synchronize by the assistance of this system call.
In its current state this system call represents a *binary semaphore* implementation.
Mutexes are locked and unlocked with no system call assistance if there is no lock contention. If a lock contention occurs, lock holder and lock contender synchronize by the assistance of this system call. In its current state this system call represents a
"binary semaphore" implementation.
.nf
.in 16
#define L4_MUTEX_LOCK 0
#define L4_MUTEX_UNLOCK 1
.nf
.in 16
#define L4_MUTEX_LOCK 0
.br
#define L4_MUTEX_UNLOCK 1
.br
.B struct l4_mutex {
.in 12
.BI "unsigned int " "lock" ";"
.in 7
.B } __attribute__((aligned(sizeof(int))));