Searched refs:instance (Results 1 - 11 of 11) sorted by relevance
| /seL4-refos-master/libs/libplatsupport/src/ |
| H A D | irqchip.h | 22 #define DEFINE_IRQCHIP_PARSER(instance, compatible_strings, parser_func) \
23 static ps_irqchip_t instance = { \
27 USED SECTION("_ps_irqchips") ps_irqchip_t *instance##_ptr = &instance
33 * property, parse it and call the callback function on each interrupt instance
39 * @param callback Pointer to a callback function that is called at each interrupt instance in the property.
|
| /seL4-refos-master/projects/util_libs/libplatsupport/src/ |
| H A D | irqchip.h | 22 #define DEFINE_IRQCHIP_PARSER(instance, compatible_strings, parser_func) \
23 static ps_irqchip_t instance = { \
27 USED SECTION("_ps_irqchips") ps_irqchip_t *instance##_ptr = &instance
33 * property, parse it and call the callback function on each interrupt instance
39 * @param callback Pointer to a callback function that is called at each interrupt instance in the property.
|
| /seL4-refos-master/projects/util_libs/libethdrivers/plat_include/am335x/ethdrivers/plat/ |
| H A D | beaglebone.h | 72 extern void I2CPinMuxSetup(unsigned int instance);
|
| /seL4-refos-master/libs/libmuslc/src/thread/ |
| H A D | pthread_barrier_wait.c | 52 struct instance struct
63 struct instance *inst;
76 /* First thread to enter the barrier becomes the "instance owner" */
78 struct instance new_inst = { 0 };
92 /* Last thread to enter the barrier wakes all non-instance-owners */
106 /* Last thread to exit the barrier wakes the instance owner */
|
| /seL4-refos-master/projects/refos/design/ |
| H A D | intro.tex | 26 \texttt{Interfaces} are a collection of (usually related) methods that usually serve to abstract a conceptual object. For instance, the \texttt{C} standard library functions \texttt{fopen}, \texttt{fscanf}, \texttt{fprintf}, \texttt{fclose} and so on form an abstract interface and provide abstraction for a file object.
36 \texttt{Dataspace servers} (henceforth also referred to as \emph{dataservers}) are servers which implement the dataspace interface (or a subset of it) in order to provide a dataspace service to clients. Dataspace servers are often designed to provide dataspaces which represent a common concept. For instance, a file server may implement the dataspace interface for files stored on disk, and an audio driver may serve audio bytestream dataspaces.
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.
124 \srv{server} indicates the name of the server that is receiving and handling the method invocation via an endpoint. For instance, \srv{procserv} and \srv{dataserv} in method descriptions refer to a process server and a data server respectively
158 Note that \refOS does not make the assumption that the kernel is able to pass message contents via the notification itself, just that the kernel is able to pass just the notification. In order for the actual message to be delivered along with the notification, the implementation of the protocol may for instance make use of a shared buffer.
|
| H A D | interface.tex | 22 In \refOS, the access to an object (the permission to invoke the methods which manage the object) is implemented using a badged endpoint capability. The badge number is used to uniquely identify the instance of an object. Since most expected implementations of these protocols likely will use a similar method to track access permissions, the term capability may be used interchangably with object in this document. For example "window capability" means a capability which represents the access to a window object.
172 Expand a given dataspace. Note that some dataspaces may not support this method as sometimes the size of a dataspace makes no sense (serial input for instance).
226 \item The dataspace is backed by somebody the receiving process trusts (the process server for instance)
|
| /seL4-refos-master/projects/refos/impl/apps/nethack/src/nethack-3.4.3/include/ |
| H A D | qt_win.h | 785 // Single-instance preservation...
788 static NetHackQtBind* instance; member in class:NetHackQtBind
|
| /seL4-refos-master/apps/nethack/src/nethack-3.4.3/include/ |
| H A D | qt_win.h | 785 // Single-instance preservation...
788 static NetHackQtBind* instance; member in class:NetHackQtBind
|
| /seL4-refos-master/kernel/manual/parts/ |
| H A D | objects.tex | 73 capability model is an instance of a \emph{segregated} (or \emph{partitioned})
|
| /seL4-refos-master/projects/refos/impl/apps/nethack/src/nethack-3.4.3/doc/ |
| H A D | Guidebook.tex | 1136 level. There are some exceptions though. For instance, fairly early
1300 your location (for instance, a trap door which drops you to a lower
1462 some types of characters (barbarians, for instance) have the necessary
1545 can achieve for each group. For instance, wizards can become highly
2341 response to the Drop command, for instance). The value specified should
|
| /seL4-refos-master/apps/nethack/src/nethack-3.4.3/doc/ |
| H A D | Guidebook.tex | 1136 level. There are some exceptions though. For instance, fairly early
1300 your location (for instance, a trap door which drops you to a lower
1462 some types of characters (barbarians, for instance) have the necessary
1545 can achieve for each group. For instance, wizards can become highly
2341 response to the Drop command, for instance). The value specified should
|
Completed in 76 milliseconds