Lines Matching refs:EH
256 Exception and probe handling (EH)
287 with a set of EH hooks as arguments:
289 'prereset' hook (may be NULL) is called during an EH reset, before any
292 'postreset' hook (may be NULL) is called after the EH reset is
297 called to perform the low-level EH reset.
305 after executing a probe-time or EH-time command via
379 advised to read SCSI EH (Documentation/scsi/scsi_eh.rst) and ATA
505 will invoke EH for the scmd, and returning 1 makes :c:func:`ata_qc_complete`
516 EH will know to handle it later. Then it calls low level libata driver's
520 completes the qc. Note that as we're currently in EH, we cannot call
521 scsi_done. As described in SCSI EH doc, a recovered scmd should be
526 If EH is invoked due to a failed ATAPI qc, the qc here is completed but
528 place holder to make EH code reach this place. This is a bit hackish,
538 Problems with the current EH
550 - EH handling via :c:func:`ata_scsi_error` is not properly protected from
551 usual command processing. On EH entrance, the device is not in
570 enter EH and trigger actions makes life painful.
572 Third, scattered EH code makes implementing low level drivers
573 difficult. Low level drivers override libata callbacks. If EH is
626 `EH recovery actions <#exrec>`__.
845 EH recovery actions
862 During EH, resetting is necessary in the following cases.
868 - EH needs to make HBA/device forget about in-flight commands
872 Resetting during EH might be a good idea regardless of error condition
873 to improve EH robustness. Whether to reset both or either one of HBA and