From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: improve AC_ERR_DEV handling for ->post_internal_cmd
Date: Tue, 17 Apr 2007 10:42:47 -0400 [thread overview]
Message-ID: <4624DCE7.8010106@garzik.org> (raw)
In-Reply-To: <20070320062411.GE6152@htj.dyndns.org>
Tejun Heo wrote:
> ->post_internal_cmd is simplified EH for internal commands. Its
> primary mission is to stop the controller such that no rogue memory
> access or other activities occur after the internal command is
> released. It may provide error diagnostics by setting qc->err_mask
> but this hasn't been a requirement.
>
> To ignore SETXFER failure for CFA devices, libata needs to know
> whether a command was failed by the device or for any other reason.
> ie. internal command needs to get AC_ERR_DEV right.
>
> This patch makes the following changes to AC_ERR_DEV handling and
> ->post_internal_cmd semantics to accomodate this need and simplify
> callback implementation.
>
> 1. As long as the correct bits in the result TF registers are set,
> there is no need to set AC_ERR_DEV explicitly. libata EH core
> takes care of that for both normal and internal commands.
>
> 2. The only requirement for ->post_internal_cmd() is to put the
> controller into quiescent state. It needs not to set any err_mask.
>
> 3. ata_exec_internal_sg() performs minimal error analysis such that
> AC_ERR_DEV is automatically set as long as result_tf is filled
> correctly.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
applied
prev parent reply other threads:[~2007-04-17 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 6:24 [PATCH] libata: improve AC_ERR_DEV handling for ->post_internal_cmd Tejun Heo
2007-04-17 14:42 ` Jeff Garzik [this message]
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=4624DCE7.8010106@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).