1. 19 2月, 2012 4 次提交
    • M
      [SCSI] pm8001: deficient responses to IO_XFER_ERROR_BREAK and IO_XFER_OPEN_RETRY_TIMEOUT · 5954d738
      Mark Salyzyn 提交于
      IO_XFER_ERROR_BREAK and IO_XFER_OPEN_RETRY_TIMEOUT are deficient of the
      required actions as outlined in the programming manual for the pm8001. Due to
      the overlapping code requirements of these recovery responses, we found it
      necessary to bundle them together into one patch.
      
      When a break is received during the command phase (ssp_completion), this is a
      result of a timeout or interruption on the bus. Logic suggests that we should
      retry the command.
      
      When a break is received during the data-phase (ssp_event), the task must be
      aborted on the target or it will retain a data-phase lock turning the target
      reticent to all future media commands yet will successfully respond to TUR,
      INQUIRY and ABORT leading eventually to target failure through several
      abort-cycle loops.
      
      The open retry interval is exceedingly short resulting in occasional target
      drop-off during expander resets or when targets push-back during bad-block
      remapping. Increased effective timeout from 130ms to 1.5 seconds for each try
      so as to trigger after the administrative inquiry/tur timeout in the scsi
      subsystem to keep error-recovery harmonics to a minimum.
      
      When an open retry timeout event is received, the action required by the
      targets is to issue an abort for the outstanding command then logic suggests
      we retry the command as this state is usually an indication of a credit block
      or busy condition on the target.
      
      We hijacked the pm8001_handle_event work queue handler so that it will handle
      task as an argument instead of device for the workers in support of the
      deferred handling outlined above.
      
      Moderate to Heavy bad-path testing on a 2.6.32 vintage kernel, compile-testing
      on scsi-misc-2.6 kernel ...
      Signed-off-by: NMark Salyzyn <mark_salyzyn@xyratex.com>
      Acked-by: NJack Wang <jack_wang@usish.com>
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      5954d738
    • M
      [SCSI] pm8001: Add FUNC_GET_EVENTS · d95d0001
      Mark Salyzyn 提交于
      Jack noticed I dropped a patch fragment associated with a flags automatic
      variable in mpi_set_phys_g3_with_ssc (ooops) and that the pre-emptive locking
      that piggy-backed this patch was not in-fact necessary because of underlying
      atomic accesses to the hardware. Here is the updated patch fixing these two
      issues.
      
      The pm8001 driver is missing the FUNC_GET_EVENTS handler in the phy control
      function. Since the pm8001_bar4_shift function was not designed to be called
      at runtime, added locking surrounding the adjustment for all accesses.
      Signed-off-by: NMark Salyzyn <mark_salyzyn@xyratex.com>
      Acked-by: NJack Wang <jack_wang@usish.com>
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      d95d0001
    • M
      [SCSI] pm8001: fix lockup on phy_control hard reset. · 5c4fb76a
      Mark Salyzyn 提交于
      pm8001_phy_control PHY_FUNC_HARD_RESET locks up on second try via
      smp_phy_control because response HW_EVENT_PHY_START_STATUS fails to complete
      previous command. The PM8001F_RUN_TIME flag is not treated as a bit, but a
      state in all readers, yet once we are operational or in the run time state,
      the flags use a bit-set operation.
      Signed-off-by: NMark Salyzyn <mark_salyzyn@xyratex.com>
      Acked-by: NJack Wang <jack_wang@usish.com>
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      5c4fb76a
    • O
      [SCSI] st: implement PM · 46a243f7
      Oliver Neukum 提交于
      This implements basic power management for SCSI tapes.
      Signed-off-by: NOliver Neukum <oneukum@suse.de>
      Acked-by: NKai Mäkisara <kai.makisara@kolumbus.fi>
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      46a243f7
  2. 18 2月, 2012 15 次提交
  3. 13 2月, 2012 1 次提交
  4. 22 1月, 2012 2 次提交
  5. 16 1月, 2012 18 次提交