/barrelfish-2018-10-04/usr/vmkitmon/ |
H A D | guest.c | 463 // run real handler 468 .handler = idc_handler, 510 .handler = idc_handler, 1480 // this handler supports only real-mode 2938 vmexit_handler handler; local 2942 handler = handle_vmexit_npf; 2944 handler = vmexit_handlers[exitcode]; 2957 handler = vmexit_handlers[saved_exit_reason]; 2963 int r = handler(g);
|
/barrelfish-2018-10-04/usr/arrakismon/ |
H A D | guest.c | 414 // run real handler 419 .handler = idc_handler, 463 .handler = idc_handler, 1256 // this handler supports only real-mode 2247 vmexit_handler handler; local 2252 handler = handle_vmexit_npf; 2254 handler = vmexit_handlers[exitcode]; 2260 int r = handler(g);
|
/barrelfish-2018-10-04/doc/013-capability-mgmt/ |
H A D | type_system.tex | 749 handler dispatcher that will be invoked when the kernel receives 777 This invocation sets the user-level handler endpoint that will receive 778 a message when the given interrupt occurs. While a handler is set, 785 This invocation clears the handler for the given IRQ. 920 \item \verb|KernelCmd_IPI_Register|: Register a handler for an IPI (?). 921 \item \verb|KernelCmd_IPI_Delete|: Delete a handler for an IPI (?).
|
/barrelfish-2018-10-04/lib/devif/backends/net/mlx4/drivers/infiniband/core/ |
H A D | sa_query.c | 568 static void ib_sa_event(struct ib_event_handler *handler, struct ib_event *event) argument 578 container_of(handler, typeof(*sa_dev), event_handler); 582 if (rdma_port_get_link_layer(handler->device, port->port_num) != IB_LINK_LAYER_INFINIBAND) 1136 * @callback:function called when notice handler registration completes, 1391 * We register our event handler after everything is set up, 1392 * and then update our cached info after the event handler is
|
H A D | multicast.c | 741 static void mcast_event_handler(struct ib_event_handler *handler, argument 747 dev = container_of(handler, struct mcast_device, event_handler);
|
H A D | notice.c | 643 static void inform_event_handler(struct ib_event_handler *handler, argument 648 dev = container_of(handler, struct inform_device, event_handler);
|
H A D | uverbs_main.c | 517 void ib_uverbs_event_handler(struct ib_event_handler *handler, argument 521 container_of(handler, struct ib_uverbs_file, event_handler);
|
/barrelfish-2018-10-04/usr/eclipseclp/ecrc_solvers/ |
H A D | chr2pl.pl | 32 op(1200, fy, handler), 57 :- dynamic (handler)/1, (constraints)/1, (label_with)/1, rule/5, (:--)/2. 130 retract_all(handler _), 175 chr_item(handler(Name)) :- atomic(Name).
|
/barrelfish-2018-10-04/usr/eclipseclp/icparc_solvers/ech/ |
H A D | puzzle_bool.pl | 78 :- [bool]. % load in boolean ECH handler
|
H A D | diaz_bool.pl | 57 :- [bool]. % load in boolean ECH handler
|
/barrelfish-2018-10-04/usr/eclipseclp/Kernel/lib/ |
H A D | bsi.pl | 247 % This leads to problems here, since the handler is called without
|
H A D | fd.pl | 2224 solution is found, the event 280 is raised, its default handler prints 2246 solution is found, the event 280 is raised, its default handler prints 2323 default handler prints the current cost. 2353 default handler prints the current cost. 2392 default handler prints the current cost. 2484 handler prints the current cost. 2509 handler prints the current cost. 2585 solution is found, the event 280 is raised, its default handler 2615 solution is found, the event 280 is raised, its default handler 2656 handler print [all...] |
/barrelfish-2018-10-04/usr/monitor/capops/ |
H A D | retype.c | 381 assert(cont.handler); 489 // setup handler for retype check result
|
/barrelfish-2018-10-04/usr/tests/bulk_transfer/ |
H A D | bulk_shm.c | 388 .handler = a2_bound_cont,
|
/barrelfish-2018-10-04/usr/eclipseclp/Opium/ |
H A D | opium_light.pl | 88 * before the scenario handler links together commands/procedures and their
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/internal/kernel/ |
H A D | runtime.tex | 205 At the next synchronous point in execution, the corresponding handler, 256 \item[Event Handler] The predicate that acts as event handler for the event 314 \item handler settings (e.g.\ event handler property)
|
/barrelfish-2018-10-04/lib/barrelfish/ |
H A D | spawn_client.c | 183 .handler = proc_mgmt_accept_recv_handler, 208 /* Run the RX handler; has a side-effect of registering for receive events */ 240 /* setup error handler */ 273 /* Register for receive notification on our special handler */ 275 .handler = proc_mgmt_accept_recv_handler, 327 /* Run the RX handler; has a side-effect of registering for receive events */
|
/barrelfish-2018-10-04/usr/replay/ |
H A D | master.c | 210 static bool bound; /* XXX: make this volatile? No, handler runs on the same context */ 731 assert(closure.handler != NULL); 732 //printf(RED("-------- GOT A MASTER EVENT handler=%p arg=%p"), closure.handler, closure.arg); 733 closure.handler(closure.arg);
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/userman/ |
H A D | umsintro.tex | 211 %When an event occurs, the corresponding {\it event handler} is called, 216 %it by defining an appropriate event handler.
|
H A D | umsopsys.tex | 298 Thus, by defining a suitable interrupt handler, it is possible to service this 384 predicate and declare it as the interrupt handler for this interrupt
|
/barrelfish-2018-10-04/lib/term/client/ |
H A D | client_blocking.c | 403 * \brief Default asynchronous error handler. 591 trigger->closure.handler(trigger->closure.arg);
|
/barrelfish-2018-10-04/doc/009-notifications/ |
H A D | Notify.tex | 217 The cap$\_$invoke handler puts the receivers's DCB pointer into the 220 The receiving core has an notification IPI handler which drains the
|
/barrelfish-2018-10-04/doc/018-Practical-guide/ |
H A D | helloWorldApp.tex | 465 kernel: 0: installing handler for IRQ 1 466 kernel: 0: installing handler for IRQ 2
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/embedding/ |
H A D | embvb.tex | 82 execution of the corresponding event handler
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/tutorial/ |
H A D | eprolog.tex | 942 When an event occurs, a call to the appropriate handler is inserted 944 The handler will be executed as soon as possible, which means at the 948 A handler is defined using a call like this 956 The handler's first argument is the event identifier, in this case the
|