diff options
| author | Thomas Schwinge <thomas@schwinge.name> | 2011-03-26 01:33:43 +0100 |
|---|---|---|
| committer | Thomas Schwinge <thomas@schwinge.name> | 2011-03-26 01:33:43 +0100 |
| commit | 48d63562b1eb3e1211fe2ad803a3df704f9c342c (patch) | |
| tree | d26a58aba6e9ffc814e88f22529bfae9db9579bf /community/gsoc/project_ideas/valgrind.mdwn | |
| parent | 2ad64644b9290ed1b63108b01ef63939adba5a93 (diff) | |
| parent | 0729272db4fe4563fee46488236d75e9c4700eee (diff) | |
| download | web-48d63562b1eb3e1211fe2ad803a3df704f9c342c.tar.gz web-48d63562b1eb3e1211fe2ad803a3df704f9c342c.tar.bz2 web-48d63562b1eb3e1211fe2ad803a3df704f9c342c.zip | |
Merge commit '0729272db4fe4563fee46488236d75e9c4700eee'
Conflicts:
community/gsoc/project_ideas/libdiskfs_locking.mdwn
Diffstat (limited to 'community/gsoc/project_ideas/valgrind.mdwn')
| -rw-r--r-- | community/gsoc/project_ideas/valgrind.mdwn | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/community/gsoc/project_ideas/valgrind.mdwn b/community/gsoc/project_ideas/valgrind.mdwn index 16cd1373..17385f75 100644 --- a/community/gsoc/project_ideas/valgrind.mdwn +++ b/community/gsoc/project_ideas/valgrind.mdwn @@ -35,14 +35,14 @@ Compared to Linux, [[microkernel/Mach]] (the microkernel used by the Hurd) has very few kernel traps. Almost all [[system call]]s are implemented as [[RPC]]s instead -- either handled by Mach itself, or by the various [[Hurd servers|hurd/translator]]. -All RPCs use a pair of `mach_msg` invocations: +All RPCs use a pair of `mach_msg()` invocations: one to send a request message, and one to receive a reply. -However, while all RPCs use the same `mach_msg` trap, +However, while all RPCs use the same `mach_msg()` trap, the actual effect of the call varies greatly depending on which RPC is invoked -- -similar to the `ioctl` call on Linux. +similar to the `ioctl()` call on Linux. Each request thus must be handled individually. -Unlike `ioctl`, +Unlike `ioctl()`, the RPC invocations have explicit type information for the parameters though, which can be retrieved from the message header. By analyzing the parameters of the RPC reply message, |