Lines Matching refs:EH
272 Exception and probe handling (EH)
311 with a set of EH hooks as arguments:
313 'prereset' hook (may be NULL) is called during an EH reset, before any
316 'postreset' hook (may be NULL) is called after the EH reset is
321 called to perform the low-level EH reset.
329 after executing a probe-time or EH-time command via
404 advised to read SCSI EH (Documentation/scsi/scsi_eh.txt) and ATA
541 will invoke EH for the scmd, and returning 1 makes :c:func:`ata_qc_complete`
556 If EH is invoked for timeout, :c:func:`ata_qc_timeout` stops BMDMA and
557 completes the qc. Note that as we're currently in EH, we cannot call
558 scsi_done. As described in SCSI EH doc, a recovered scmd should be
563 If EH is invoked due to a failed ATAPI qc, the qc here is completed but
565 place holder to make EH code reach this place. This is a bit hackish,
575 Problems with the current EH
587 - EH handling via :c:func:`ata_scsi_error` is not properly protected from
588 usual command processing. On EH entrance, the device is not in
607 enter EH and trigger actions makes life painful.
609 Third, scattered EH code makes implementing low level drivers
610 difficult. Low level drivers override libata callbacks. If EH is
663 `EH recovery actions <#exrec>`__.
882 EH recovery actions
899 During EH, resetting is necessary in the following cases.
905 - EH needs to make HBA/device forget about in-flight commands
909 Resetting during EH might be a good idea regardless of error condition
910 to improve EH robustness. Whether to reset both or either one of HBA and