Lines Matching defs:IOWorkLoop
47 /*! @class IOWorkLoop
48 @discussion An IOWorkLoop is a thread of control that is intended to be used to provide single threaded access to hardware. This class has no knowledge of the nature and type of the events that it marshals and forwards. When a device driver successfully starts (see IOService::start), it is expected to create the event sources it will need to receive events. Then a work loop is initialized and the events are added to the work loop for monitoring. In general this set up will be automated by the family superclass of the specific device.
54 class IOWorkLoop : public OSObject
56 OSDeclareDefaultStructors(IOWorkLoop)
85 static void threadMainContinuation(IOWorkLoop *self);
89 IOWorkLoop uses this to determine if the event source should be polled in runEventSources() or not.
105 This is a recursive lock, which allows multiple layers of code to share a single IOWorkLoop without deadlock. This is common in IOKit since threads of execution tend to follow the service plane in the IORegistry, and multiple objects along the call path may acquire the gate for the same (shared) workloop.
140 @discussion This structure will be used to expand the capablilties of the IOWorkLoop in the future.
191 static IOWorkLoop *workLoop();
198 static IOWorkLoop *workLoopWithOptions(IOOptionBits options);
321 OSMetaClassDeclareReservedUnused(IOWorkLoop, 0);
322 OSMetaClassDeclareReservedUnused(IOWorkLoop, 1);
323 OSMetaClassDeclareReservedUnused(IOWorkLoop, 2);
325 OSMetaClassDeclareReservedUsed(IOWorkLoop, 0);
326 OSMetaClassDeclareReservedUsed(IOWorkLoop, 1);
327 OSMetaClassDeclareReservedUsed(IOWorkLoop, 2);
329 OSMetaClassDeclareReservedUnused(IOWorkLoop, 3);
330 OSMetaClassDeclareReservedUnused(IOWorkLoop, 4);
331 OSMetaClassDeclareReservedUnused(IOWorkLoop, 5);
332 OSMetaClassDeclareReservedUnused(IOWorkLoop, 6);
333 OSMetaClassDeclareReservedUnused(IOWorkLoop, 7);