Searched refs:blocked (Results 1 - 14 of 14) sorted by relevance
/seL4-refos-master/projects/refos/impl/apps/nethack/src/nethack-3.4.3/include/ |
H A D | prop.h | 114 /*** Property is blocked by an object ***/ 115 long blocked; /* Same assignments as extrinsic */ member in struct:prop
|
H A D | youprop.h | 18 * BXxx refers to the cause of the property being blocked. 166 #define BClairvoyant u.uprops[CLAIRVOYANT].blocked 185 #define BInvis u.uprops[INVIS].blocked 196 #define BStealth u.uprops[STEALTH].blocked
|
H A D | winX.h | 170 boolean blocked; /* */ member in struct:text_info_t
|
/seL4-refos-master/apps/nethack/src/nethack-3.4.3/include/ |
H A D | prop.h | 114 /*** Property is blocked by an object ***/ 115 long blocked; /* Same assignments as extrinsic */ member in struct:prop
|
H A D | youprop.h | 18 * BXxx refers to the cause of the property being blocked. 166 #define BClairvoyant u.uprops[CLAIRVOYANT].blocked 185 #define BInvis u.uprops[INVIS].blocked 196 #define BStealth u.uprops[STEALTH].blocked
|
H A D | winX.h | 170 boolean blocked; /* */ member in struct:text_info_t
|
/seL4-refos-master/projects/util_libs/libethdrivers/src/plat/am335x/ |
H A D | lwiplib.h | 224 u32_t blocked; member in struct:cpsw_switch_param
|
/seL4-refos-master/projects/refos/impl/apps/nethack/src/nethack-3.4.3/src/ |
H A D | worn.c | 45 /* Updated to use the extrinsic and blocked fields. */ 75 u.uprops[p].blocked &= ~wp->w_mask; 95 u.uprops[p].blocked |= wp->w_mask; 107 /* Updated to use the extrinsic and blocked fields. */ 126 u.uprops[p].blocked &= ~wp->w_mask;
|
/seL4-refos-master/apps/nethack/src/nethack-3.4.3/src/ |
H A D | worn.c | 45 /* Updated to use the extrinsic and blocked fields. */ 75 u.uprops[p].blocked &= ~wp->w_mask; 95 u.uprops[p].blocked |= wp->w_mask; 107 /* Updated to use the extrinsic and blocked fields. */ 126 u.uprops[p].blocked &= ~wp->w_mask;
|
/seL4-refos-master/kernel/manual/parts/ |
H A D | ipc.tex | 203 thread may have been blocked on the endpoint for some time before it 246 Then, the caller thread is blocked waiting for the reply.
|
H A D | objects.tex | 222 the calling thread is blocked until a capability to the reply object is 277 scheduled, blocked, unblocked, etc., depending on the application's
|
H A D | threads.tex | 188 suspending a thread, in that threads that are blocked waiting in an endpoint or notification queue 246 a notification object with a passive thread blocked waiting on it, the passive thread will receive
|
/seL4-refos-master/projects/refos/design/ |
H A D | intro.tex | 112 Most of the interface methods are synchronous. The client making the call is considered to be less trusted than the server that is receiving the call. When a client makes a call, it is blocked until the server finishes handling the call and replies via the reply operation. When the server replies, the call is said to be finished and the client resumes execution. Method invocation is implemented with a synchronous call operation via a synchronous endpoint. Capabilities may be passed via method invocation and also via the corresponding reply.
|
H A D | protocol.tex | 433 An anonymous dataspace data structure needs to bookkeep its capability, the list of frame pages it is representing and its content initialisation data. The content initialisation bitmask records which pages in the dataspace have been initialised and which still need to be initialised. Initialisation happens lazily, on the first VM fault, so a waiting list of clients that are VM fault blocked waiting for content to be initialised needs to be recorded.
|
Completed in 172 milliseconds