Lines Matching full:all

19 halting all I/O to it.  The goal of a disconnection is to avoid system
31 is reported as soon as possible to all affected device drivers,
47 After a reset and/or a re-enabling of I/O, all drivers are
49 that may be required.  After these have all completed, a final
57 through a large number of contortions to complete recovery. Almost all
107 A driver does not have to implement all of these callbacks; however,
122 is isolated, in that all I/O is blocked: all reads return 0xffffffff,
123 all writes are ignored.
141 All drivers participating in this system must implement this call.
153       Driver returns this if it doesn't want to recover at all.
158 If all drivers on the segment/slot return PCI_ERS_RESULT_CAN_RECOVER,
173    implementation uses one kernel thread to notify all devices;
174    thus, if one device sleeps/schedules, all devices are affected.
176    recovery implementation (e.g. waiting for all notification threads
191 DMA), and then calls the mmio_enabled() callback on all affected
199 all drivers on a segment agree that they can try to recover and if no automatic
207    Proposal: All I/Os should be done _synchronously_ from within
236 If all drivers returned PCI_ERS_RESULT_RECOVERED, then the platform
292 at this point.  If all device drivers report success on this
338 The platform will call the resume() callback on all affected device
339 drivers if all drivers on the segment have returned
355 cancel all pending I/O, refuse all new I/O, returning -EIO to
356 higher layers. The device driver should then clean up all of its
363 Note, however, not all failures are truly "permanent". Some are
410    patches implementing error recovery. Not all of these patches are in