Searched refs:how (Results 51 - 58 of 58) sorted by relevance
123
| /seL4-refos-master/kernel/manual/parts/ |
| H A D | bootup.tex | 123 describes what the chunk is and how long it is, where the length includes the header. The
164 This, along with knowledge of how capabilities in \texttt{userImageFrames} and
|
| H A D | cspace.tex | 51 capability and CSpace management, before discussing how capabilities
52 are addressed within CSpaces, i.e. how applications can refer to
192 the various capability types, and how capability-derivation failures
476 occur at varying offsets in the IPC buffer depending on how the error
|
| H A D | objects.tex | 47 This chapter gives an overview of these services, describes how kernel
48 objects are accessed by userspace applications, and describes how new
423 a \emph{watermark} recording how much of the region has previously been
448 When retyping untyped memory it is useful to know how much memory the
|
| H A D | ipc.tex | 15 and how they can be used for communication between applications.
|
| H A D | threads.tex | 143 Round-robin threads are treated that same as sporadic threads except for one case: how the
|
| /seL4-refos-master/projects/refos/impl/apps/nethack/src/nethack-3.4.3/src/ |
| H A D | zap.c | 2466 /* [how about `bhitpile(u.ustuck->minvent)' effect?] */
3935 const char *how = destroy_strings[dindx * 3 + 2]; local
3938 losehp(dmg, one ? how : (const char *)makeplural(how),
|
| /seL4-refos-master/apps/nethack/src/nethack-3.4.3/src/ |
| H A D | zap.c | 2466 /* [how about `bhitpile(u.ustuck->minvent)' effect?] */
3935 const char *how = destroy_strings[dindx * 3 + 2]; local
3938 losehp(dmg, one ? how : (const char *)makeplural(how),
|
| /seL4-refos-master/projects/refos/design/ |
| H A D | interface.tex | 215 Give the content from the local dataserver to the remote dataserver in response to the remote dataserver's earlier notification asking for content. The content is assumed to be in the set up parameter buffer. This call implicitly requires a parameter buffer to be set up, and how this is done is up to the implementation. Even though the notification from the dataserver asking for content uses an ID to identify the dataspace, the reply, for security reasons, gives the actual dataspace capability. The ID may be used securely if the dataserver implementation supports per-client ID checking, and in this situtation a version of this method with an ID instead of a capability could be added.
|
Completed in 117 milliseconds
123