From: Jeff Garzik <jgarzik@pobox.com>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: Mark Lord <mlord@pobox.com>
Subject: A note on libata passthru patch
Date: Sun, 21 Aug 2005 17:37:18 -0400 [thread overview]
Message-ID: <4308F40E.3010109@pobox.com> (raw)
Something that Alan unintentionally reminded me, about the libata
passthru patch: Some controllers require certain ATA commands to be
synchronized at the host-wide level.
An example is SET FEATURES - XFER MODE on Promise controllers. The
controller snoops the taskfile for the xfer mode, and uses that info to
program certain timing-related registers. If you issue a SET FEATURES -
XFER MODE command on one port while doing data xfer on another port,
then data corruption can occur.
I'm pretty sure at least one other controller does similar taskfile
snooping.
Currently probing is 100% synchronous, so our internal use of SET
FEATURES - XFER MODE is safe. But when you turn on ATA passthru, it is
not safe.
This is another issue that needs fixing before we can merge the ATA
passthru feature, since the consequences can be serious.
Jeff
next reply other threads:[~2005-08-21 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 21:37 Jeff Garzik [this message]
2005-08-21 21:44 ` A note on libata passthru patch Mark Lord
2005-08-21 21:46 ` Jeff Garzik
2005-08-22 12:26 ` John W. Linville
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=4308F40E.3010109@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=mlord@pobox.com \
/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).