Lines Matching refs:upcall

280   upcall is dispatched to Venus by creating a message structure.  The
288   synchronization objects.  In the upcall routine the message structure
290   queue.  The routine calling upcall is responsible for allocating the
295   the OS. This notification is done in the upcall context of the process
297   in upcall.  The (kernel mode) processing of P in the filesystem
299   the calling thread in P is blocked in upcall.  A pointer in the
320      processing its upcall with the data buffer replaced with the reply
328   Now P awakes and continues processing upcall.  There are some
330   up in upcall by a signal from some other source (for example an
332   sendmsg_to_kernel call.  In the normal case, the upcall routine will
352   involves more than one upcall, this can lead to complicated state, an
544   The path must be a Coda file, otherwise the ioctl upcall will not be
759   DDeessccrriippttiioonn  This upcall is invoked to request creation of a file.
1191   DDeessccrriippttiioonn This upcall asks Venus to do a get operation on an fsobj
1288   DDeessccrriippttiioonn This upcall asks Venus to read or write from a file.
1401   SSuummmmaarryy Send Venus a signal about an upcall.
1410   DDeessccrriippttiioonn  This is an out-of-band upcall to Venus to inform Venus
1418   it is doing this correctly.  Also we need to handle multiple upcall
1420   what state changes in Venus take place after an upcall for which the
1640   +o  Close will notify any sleeping processes that their upcall cannot