Searched refs:system (Results 1 - 25 of 36) sorted by relevance

12

/seL4-refos-master/kernel/include/model/
H A Dsmp.h18 nodeState_t system; member in struct:smpStatedata
H A Dstatedata.h29 #define NODE_STATE_ON_CORE(_state, _core) ksSMP[(_core)].system._state
/seL4-refos-master/libs/libmuslc/src/internal/microblaze/
H A Dsyscall.s5 addi r12, r5, 0 # Save the system call number
/seL4-refos-master/libs/libmuslc/src/internal/powerpc/
H A Dsyscall.s5 mr 0, 3 # Save the system call number
/seL4-refos-master/libs/libmuslc/src/internal/powerpc64/
H A Dsyscall.s5 mr 0, 3 # Save the system call number
/seL4-refos-master/libs/libplatsupport/src/plat/bcm2837/
H A Dltimer.c36 system_timer_t system; member in struct:__anon20
105 system_timer_handle_irq(&spt_ltimer->system);
127 *time = system_timer_get_time(&spt_ltimer->system);
144 return system_timer_set_timeout(&spt_ltimer->system, ns);
161 system_timer_reset(&spt_ltimer->system);
250 /* Setup system timer */
255 system_timer_init(&spt_ltimer->system, system_config);
/seL4-refos-master/projects/util_libs/libplatsupport/src/plat/bcm2837/
H A Dltimer.c36 system_timer_t system; member in struct:__anon61
105 system_timer_handle_irq(&spt_ltimer->system);
127 *time = system_timer_get_time(&spt_ltimer->system);
144 return system_timer_set_timeout(&spt_ltimer->system, ns);
161 system_timer_reset(&spt_ltimer->system);
250 /* Setup system timer */
255 system_timer_init(&spt_ltimer->system, system_config);
/seL4-refos-master/projects/refos/impl/
H A DMakefile99 qemu-system-arm -nographic -M kzm \
103 qemu-system-i386 \
108 qemu-system-i386 \
130 @echo " make simulate-kzm - Boot kzm configured system image."
131 @echo " make simulate-ia32 - Boot ia32 configured system image."
132 @echo " make simulate-ia32-graphics - Boot ia32 configured system image in new console."
/seL4-refos-master/
H A DMakefile99 qemu-system-arm -nographic -M kzm \
103 qemu-system-i386 \
108 qemu-system-i386 \
130 @echo " make simulate-kzm - Boot kzm configured system image."
131 @echo " make simulate-ia32 - Boot ia32 configured system image."
132 @echo " make simulate-ia32-graphics - Boot ia32 configured system image in new console."
/seL4-refos-master/libs/libmuslc/src/process/
H A Dsystem.c12 int system(const char *cmd) function
/seL4-refos-master/projects/util_libs/liblwip/include/lwip/arch/
H A Dcc.h34 # error Unable to detemine system endianess
/seL4-refos-master/projects/refos/design/
H A Dpaper.tex131 The design of a multi-server operating system is crucial to its efficiency, security and dependability. Increasing usage of embedded systems and microcontroller chips has increased the interest from both industrial and academic communities in microkernel-based component-based software systems. This has resulted in heightened interest in developing better systems and more advanced microkernels.
133 This document outlines a basic reference design for system components and interfaces for an operating system. The protocols have been designed with an \Lf like microkernel in mind and assume functionality such as interprocess communcation, capability-based access models and virtual memory support. This reference design aims to standardise the protocols for tasks often required to build a system such as resource sharing, virtual memory management and naming. Operating systems may implement these protocols and extend them to incorporate more features.
135 A sample implementation of the following protocols is provided in addition to this document in the form of a simple operating system which runs simple client programs. The sample implementation, named \refOS, runs on the \seLf microkernel, which adds an extra dimension of dependability. Although this document outlines the major design strategies that \refOS employs, the doxygen code documentation provides additional details about \refOS.
188 This paper presents a reference design for a multi-server operating system designed for an \texttt{L4} based microkernel. It outlines a set of minimal design abstractions and methodologies which provide a standard protocol for common tasks and sample message sequences. In addition to this document, \refOS provides a documented sample implementation of this protocol. For more information about \refOS, refer to the doxygen code documentation.
H A Dintro.tex13 This document explains the abstract protocols for a multi-server microkernel based operating system.
17 The dataspace abstraction which dataspace servers provide paves the way for more complicated infrastructure such as sharing with complex trust relationships, memory management, file systems, and distributed naming. On top of this additional infrastructure, an operating system could implement features such as POSIX standard system calls, ports of existing software, drivers and display servers.
30 \texttt{Protocols} here refer to a collection of interfaces, their methods, message sequences and system components.
38 \texttt{Process servers} are servers which implement the process server interface and provide process abstraction. In practice, the process server may also need to implement additional interfaces and provide additional functionality in order for a system to start. For instance, in \refOS the process server also does naming and console input and output, implements the dataspace interface for anonymous memory and acts as the memory manager.
86 \autoref{fig:mta} presents the four basic operations \refOS employs (and indirectly attempts to limit itself to). They are synchronous calls (a method invocation on an object), replies, asynchronous notifications, and kernel system calls that asynchronously modify the state of another process (such as mapping memory directly into the virtual address space of another process).
H A Dinterface.tex13 This chapter explains the interfaces which make up the \refOS protocol. These interfaces set the language with which components in the system interact. Interfaces are intended to provide abstractions to manage conceptual objects such as a processes, files and devices.
15 Further implementations beyond \refOS may choose to extend these interfaces to provide extra system functionality and to attach additional interfaces.
91 Register to receive faults for the presented window. The returned \ty{window\_id} is an integer used during notification in order for the pager to be able to identify which window faulted. \ty{window\_id} must be unique for each pager, although each \ty{window\_id} may also be implemented to be unique across the entire system.
139 The server connection interface enables client session connection and disconnection. It may be a good idea during implementation to extend this interface onto any other extra operating system functionality that is common across servers. This could include debug ping, parameter buffer setup and notification buffer setup.
268 Return an anon capability if the server is found. This method resolves part of the path string returned as an offset into the path string that has been resolved. The rest of the path string may be resolved by other dataspaces until the system reaches the endpoint to the server that contains the file that it is searching for. This allows for a simple hierachical namespace with distributed naming.
279 \refOS follows the component-based multi-server operating system design. The two main components in the design are the process server and the file server. \refOS implements an additional operating system server which is a dataserver that is responsible for basic device related tasks.
284 The process server is the most trusted component in the system. It runs as the initial kernel thread and does not depend on any other component (this avoids deadlock). The process server implementation is single-threaded. The process server also implements the dataspace interface for anonymous memory and acts as the memory manager.
/seL4-refos-master/kernel/manual/parts/
H A Dobjects.tex11 primitives. In this way, the functionality of the system can be extended
17 MCS\footnote{``mixed-criticality system''} support.
58 With this, the system can be configured to isolate software components from
74 capability system, where capabilities are managed by the kernel.
95 capabilities through the system is controlled by a
130 % making these prose descriptions of the system calls legitimate targets for
133 Fundamentally, we can regard the kernel as providing three system calls:
146 appropriate one. The \emph{Yield} system call is not associated with any kernel
152 The fundamental system calls are:
154 \item[\apifunc{seL4\_Yield}{sel4_yield}] is the only system cal
[all...]
H A Dipc.tex101 threads. \obj{Endpoint} objects are invoked directly using the seL4 system calls
108 system calls will wait in a queue for the first available receiver. Likewise, if
110 system call or the second half of \apifunc{seL4\_ReplyRecv}{sel4_replyrecv}
190 reason, \apifunc{seL4\_Send}{sel4_send} and \apifunc{seL4\_Call}{sel4_call} system calls immediately abort and
191 no IPC or capability transfer takes place. The system call will return
202 performs the send system call, this error may still occur. The sending
209 system call, the \apifunc{seL4\_Recv}{sel4_recv} system call does not check that the
211 Hence, the \apifunc{seL4\_Recv}{sel4_recv} system call will not fail with an error if the
280 efficiency reasons (combining two operations into a single system
[all...]
H A Dio.tex40 When the system first starts, no \obj{IRQHandler} capabilities are
44 system. Typically, the initial thread of a system will determine which
45 IRQs are required by other components in the system, produce an
101 At system initialisation, the initial thread's \obj{CSpace} contains the
117 device, restricting the regions of system memory that it can access.
186 which allows system software to manage access rights and address translation for
194 to stages in the ArmV8 virtual memory system architecture such as either
216 The seL4 API allows system software to manage an SMMU by assigning StreamIDs to
219 This allows system softwar
[all...]
H A Dintro.tex11 The seL4 microkernel is an operating-system kernel designed to be
H A Dapi.tex109 seL4 system calls return an error code in the message tag and a short
257 This section provides the system call API for non-MCS kernel configurations.
261 This section provides the system call API for MCS kernel configurations.
/seL4-refos-master/libs/libmuslc/include/
H A Dstdlib.h53 int system (const char *);
/seL4-refos-master/libs/libmuslc/src/thread/powerpc/
H A Dsyscall_cp.s45 mr 0, 4 # put the system call number into r0
/seL4-refos-master/projects/refos/impl/apps/nethack/src/nethack-3.4.3/include/
H A Dsystem.h1 /* SCCS Id: @(#)system.h 3.4 2001/12/07 */
12 /* some old <sys/types.h> may not define off_t and size_t; if your system is
51 /* You may want to change this to fit your system, as this is almost
231 /* these aren't quite right, but this saves including lots of system files */
280 E int FDECL(system, (const char *));
289 E int FDECL(system, (const char *));
441 * If your system doesn't agree with this breakdown, you may want to change
443 * If your system defines sprintf, et al, in stdio.h, add to the initial
/seL4-refos-master/apps/nethack/src/nethack-3.4.3/include/
H A Dsystem.h1 /* SCCS Id: @(#)system.h 3.4 2001/12/07 */
12 /* some old <sys/types.h> may not define off_t and size_t; if your system is
51 /* You may want to change this to fit your system, as this is almost
231 /* these aren't quite right, but this saves including lots of system files */
280 E int FDECL(system, (const char *));
289 E int FDECL(system, (const char *));
441 * If your system doesn't agree with this breakdown, you may want to change
443 * If your system defines sprintf, et al, in stdio.h, add to the initial
/seL4-refos-master/projects/refos/impl/apps/nethack/src/nethack-3.4.3/sys/share/
H A Dpcsys.c93 suspend_nhwindows("To return to NetHack, enter \"exit\" at the system prompt.\n");
104 if (system(comspec) < 0) { /* wsu@eecs.umich.edu */
/seL4-refos-master/apps/nethack/src/nethack-3.4.3/sys/share/
H A Dpcsys.c93 suspend_nhwindows("To return to NetHack, enter \"exit\" at the system prompt.\n");
104 if (system(comspec) < 0) { /* wsu@eecs.umich.edu */

Completed in 134 milliseconds

12