From: Robert Hancock <hancockrwd@gmail.com>
To: Michal Soltys <soltys@ziu.info>
Cc: linux-ide@vger.kernel.org
Subject: Re: Question regarding FUA state
Date: Thu, 23 Jul 2009 00:06:38 -0600 [thread overview]
Message-ID: <4A67FDEE.2090700@gmail.com> (raw)
In-Reply-To: <4A676332.6080205@ziu.info>
On 07/22/2009 01:06 PM, Michal Soltys wrote:
> What is the current state of fua ?
>
> While peeking over older (mainly 2007ish) threads, there was some
> discussion about it - whenever it should or shouldn't be enabled by
> default, automatic blacklisting for certain controllers (some SiI 3xxx,
> others ...).
>
> http://marc.info/?l=git-commits-head&m=114110310308542&w=2
> http://marc.info/?t=117125096400001&r=2&w=2
> http://marc.info/?t=117193493900004&r=1&w=2
> http://marc.info/?t=118243369000005&r=1&w=2
>
> Current state is "disabled by default", but simple libata module
> parameter can enable it. How safe is that these days, and if enabled,
> will problematic chipsets be blacklisted automtically ? (I didn't find
> anything in the sources suggesting it happens, but I didn't look too
> thoroughly either).
>
> How do the following chipsets handle it:
>
> - ICH8R and newer ones
> - ATI's SB700/SB800 ones
> - JMB36x
> - which (if any) SiI chipsets are ok
AFAIK the only chipset that is known to have any problems are the SiI
311x, specifically with non-NCQ FUA writes (well, this chipset doesn't
do NCQ anyway). In its case it seems to be because that chipset
interprets the ATA command code in order to figure out what protocol is
being used and it doesn't seem to know about the WRITE DMA FUA opcode.
Looking at the docs it appears that the driver could work around this by
issuing some vendor-specific commands to set the protocol for that
command, but that code isn't currently in place.
Anything AHCI shouldn't care as the controller is not supposed to be
interpreting the command code. It's possible that other SFF-type SATA
controllers could have issues if they don't know about the FUA opcode.
prev parent reply other threads:[~2009-07-23 6:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 19:06 Question regarding FUA state Michal Soltys
2009-07-23 6:06 ` Robert Hancock [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=4A67FDEE.2090700@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=soltys@ziu.info \
/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).