From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
"Darrick J. Wong" <djwong@us.ibm.com>
Subject: Re: [PATCH 2/5] aic94xx: plumb in I_T_nexus_reset task management function
Date: Sun, 24 Feb 2008 00:51:55 -0500 [thread overview]
Message-ID: <47C105FB.8090401@garzik.org> (raw)
In-Reply-To: <1203831446.3139.21.camel@localhost.localdomain>
James Bottomley wrote:
> Currently aic94xx has no exported I_T_nexus_reset function. This is a
> bit of a huge problem, since sas_ata relies on this function to
> perform an ATA phy reset and also it means that if abort fails, we
> really have no bigger hammer to hit everything with.
>
> Plumb in the I_T_nexus_reset by quiescing the sequencer, sending the
> correct phy reset (link for ATA and hard for SAS) and then carefully
> resuming the sequencer again.
>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> ---
> drivers/scsi/aic94xx/aic94xx.h | 1 +
> drivers/scsi/aic94xx/aic94xx_init.c | 2 +-
> drivers/scsi/aic94xx/aic94xx_tmf.c | 58 ++++++++++++++++++++++++++++++++--
> 3 files changed, 56 insertions(+), 5 deletions(-)
Tangent:
Now that patches for ipr and sata_sx4 exist, libsas is the last holdout
using libata's old error handling paths.
I think Darrick was either scoping that work, or had preliminary patches?
Anyway, that's holding back removal of a lot of libata code, so I wanted
to make sure the issue remained in people's minds...
Jeff
next prev parent reply other threads:[~2008-02-24 5:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 5:37 [PATCH 2/5] aic94xx: plumb in I_T_nexus_reset task management function James Bottomley
2008-02-24 5:51 ` Jeff Garzik [this message]
2008-02-24 6:01 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47C105FB.8090401@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=djwong@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox