/seL4-camkes-master/projects/musllibc/src/network/ |
H A D | shutdown.c | 4 int shutdown(int fd, int how) argument 6 return socketcall(shutdown, fd, how, 0, 0, 0, 0);
|
/seL4-camkes-master/projects/musllibc/src/signal/ |
H A D | sigprocmask.c | 4 int sigprocmask(int how, const sigset_t *restrict set, sigset_t *restrict old) argument 6 int r = pthread_sigmask(how, set, old);
|
/seL4-camkes-master/projects/musllibc/src/thread/ |
H A D | pthread_sigmask.c | 5 int pthread_sigmask(int how, const sigset_t *restrict set, sigset_t *restrict old) argument 8 if ((unsigned)how - SIG_BLOCK > 2U) return EINVAL; 9 ret = -__syscall(SYS_rt_sigprocmask, how, set, old, _NSIG/8);
|
/seL4-camkes-master/tools/rumprun/lib/librumprun_base/ |
H A D | signals.c | 68 _sys___sigprocmask14(int how, const sigset_t *set, sigset_t *oset) argument
|
/seL4-camkes-master/projects/musllibc/src/internal/sh/ |
H A D | syscall.s | 7 ! Since we do not actually know how many arguments are being passed, we will
|
/seL4-camkes-master/projects/lwip/src/include/lwip/ |
H A D | sockets.h | 578 int lwip_shutdown(int s, int how); 618 #define shutdown(s,how) lwip_shutdown(s,how)
|
/seL4-camkes-master/projects/lwip/src/api/ |
H A D | api_lib.c | 106 static err_t netconn_close_shutdown(struct netconn *conn, u8_t how); 1085 * @param how fully close or only shutdown one side? 1089 netconn_close_shutdown(struct netconn *conn, u8_t how) argument 1093 LWIP_UNUSED_ARG(how); 1101 API_MSG_VAR_REF(msg).msg.sd.shut = how;
|
H A D | sockets.c | 2189 * @param opts what to update and how 2655 lwip_shutdown(int s, int how) 2661 LWIP_DEBUGF(SOCKETS_DEBUG, ("lwip_shutdown(%d, how=%d)\n", s, how)); 2680 if (how == SHUT_RD) { 2682 } else if (how == SHUT_WR) { 2684 } else if (how == SHUT_RDWR) {
|
/seL4-camkes-master/kernel/manual/parts/ |
H A D | io.tex | 159 There is presently no way to query seL4 for how many Domain IDs are supported by 273 The Arm SMMU 2.0 specification doesn't specify how StreamIDs need to correspond 274 to different devices. Each platform can define its own policy for how StreamIDs 284 \obj{seL4\_ARM\_SIDControl} capability knows about how StreamIDs are 401 The kernel does not impose any restrictions on how a VSpace is used by user-level 414 change until the VSpace is deleted. Recording how many context banks are using a 425 By knowing how many context banks are using an ASID, the kernel can easily check
|
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-camkes-master/tools/rumprun/platform/xen/xen/arch/x86/ |
H A D | x86_32.S | 148 # region the interrupted handler was executing, and so how many saved
|
/seL4-camkes-master/tools/cogent/cogent/manual/ |
H A D | cogent-manual.tex | 271 the way how values can be used in a program. 706 in the program, in particular, how \textit{often} it may be used. This concept is known as \textit{linear types}, 735 In order to decouple the property of linearity somewhat from the way how types are composed, the concept of 1264 As usual in programming languages, an \textit{expression} denotes a way how to calculate a value. The actual calculation of a value according 1992 value with a copy of readonly type. Observing variables is the only way how values of readonly types can be
|
/seL4-camkes-master/tools/cogent/cogent/doc/ |
H A D | doc.tex | 801 \TODO{How C code is generated? how to use the compiler and its intermediate outputs? What are the must-knows in the compiler?}
|