Lines Matching full:recovery
4 PCI Error Recovery
26 of a bus disconnection, and then performing error recovery.
29 Reporting and recovery is performed in several steps. First, when
38 Next, recovery is performed in several stages. Most of the complexity
57 through a large number of contortions to complete recovery. Almost all
61 device drivers already handle very similar recovery procedures;
72 The error recovery API support is exposed to the driver in the form of
75 and the actual recovery steps taken are platform dependent. The
112 for recovery. Typically a driver will want to know about
167 particular, if the platform doesn't isolate slots), and recovery
171 then recovery proceeds to STEP 4 (Slot Reset).
183 recovery implementation (e.g. waiting for all notification threads
184 to "join" before proceeding with recovery.) This seems excessively
201 This is the "early recovery" call. IOs are allowed again, but DMA is
237 segment, and thus invalidate the recovery that other devices
257 Same as above. Total failure, no recovery even after
295 For most PCI devices, a soft reset will be sufficient for recovery.
298 for recovery.
371 a new error recovery sequence.
392 errors. See the discussion in Documentation/arch/powerpc/eeh-pci-error-recovery.rst
408 That is, the recovery API only requires that:
432 the file Documentation/arch/powerpc/eeh-pci-error-recovery.rst
435 patches implementing error recovery. Not all of these patches are in