Searched refs:terminate (Results 1 - 5 of 5) sorted by relevance

/darwin-on-arm/xnu/bsd/netinet6/
H A Dipcomp_core.c274 goto terminate;
297 goto terminate;
332 terminate:
/darwin-on-arm/xnu/iokit/Kernel/
H A DIOCatalogue.cpp550 // terminate instances.
565 if ( !service->terminate(kIOServiceRequired|kIOServiceSynchronous) ) {
635 * in such a case the unload would fail so let's not terminate any
H A DIOService.cpp1855 // wait to become the terminate thread
1877 IOLog("%s::terminate(kIOServiceSynchronous) timeout\n", getName());
2249 TLOG("iokit terminate done, %d stops remain\n", gIOStopList->getCount());
2279 /* we come down here on programmatic terminate */
2317 ok = client->terminate( options );
2324 bool IOService::terminate( IOOptionBits options ) function in class:IOService
H A DIOUserClient.cpp4107 if ( !service->terminate( kIOServiceRequired
/darwin-on-arm/xnu/iokit/IOKit/
H A DIOService.h81 // options for terminate()
85 // options for registerService() & terminate()
322 @param options Options originally passed to terminate, plus <code>kIOServiceRecursing</code>.
331 @param options Options originally passed to terminate.
340 @param options Options originally passed to terminate.
545 /*! @function terminate
547 @discussion Registering an IOService object informs possible clients of its existance and instantiates drivers that may be used with it; <code>terminate</code> involves the opposite process of informing clients that an IOService object is no longer able to be used and will be destroyed. By default, if any client has the service open, <code>terminate</code> fails. If the <code>kIOServiceRequired</code> flag is passed however, <code>terminate</code> will be successful though further progress in the destruction of the IOService object will not proceed until the last client has closed it. The service will be made inactive immediately upon successful termination, and all its clients will be notified via their @link message message@/link method with a message of type <code>kIOMessageServiceIsTerminated</code>. Both these actions take place on the caller's thread. After the IOService object is made inactive, further matching or attach calls will fail on it. Each client has its @link stop stop@/link method called upon their close of an inactive IOService object , or on its termination if they do not have it open. After <code>stop</code>, @link detach detach@/link is called in each client. When all clients have been detached, the @link finalize finalize@/link method is called in the inactive service. The termination process is inherently asynchronous because it will be deferred until all clients have chosen to close.
548 @param options In most cases no options are needed. <code>kIOServiceSynchronous</code> may be passed to cause <code>terminate</cod
[all...]

Completed in 60 milliseconds