Lines Matching refs:recovery

25 of a bus disconnection, and then performing error recovery.
28 Reporting and recovery is performed in several steps. First, when
37 Next, recovery is performed in several stages. Most of the complexity
56 through a large number of contortions to complete recovery. Almost all
60 device drivers already handle very similar recovery procedures;
70 The error recovery API support is exposed to the driver in the form of
73 and the actual recovery steps taken are platform dependent.  The
106 is assumed that the driver is not doing any direct recovery and requires
155 particular, if the platform doesn't isolate slots), and recovery
159 then recovery proceeds to STEP 4 (Slot Reset).
169 >>> recovery implementation (e.g. waiting for all notification threads
170 >>> to "join" before proceeding with recovery.)  This seems excessively
187 This is the "early recovery" call. IOs are allowed again, but DMA is
203 >>> segment, and thus invalidate the recovery that other devices
223 		  Same as above. Total failure, no recovery even after
277 For most PCI devices, a soft reset will be sufficient for recovery.
280 for recovery.
351 a new error recovery sequence.
372 errors. See the discussion in powerpc/eeh-pci-error-recovery.txt
388 That is, the recovery API only requires that:
410 >>> the file Documentation/powerpc/eeh-pci-error-recovery.txt
413 >>> patches implementing error recovery. Not all of these patches are in