From: Tejun Heo <tj@kernel.org>
To: Jian Peng <jipeng@broadcom.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jgarzik@pobox.com" <jgarzik@pobox.com>,
ide <linux-ide@vger.kernel.org>
Subject: Re: questions regarding possible violation of AHCI spec in AHCI driver
Date: Wed, 08 Dec 2010 19:52:27 +0100 [thread overview]
Message-ID: <4CFFD3EB.10800@kernel.org> (raw)
In-Reply-To: <E18F441196CA634DB8E1F1C56A50A874319FA7E36E@IRVEXCHCCR01.corp.ad.broadcom.com>
Hello,
On 12/08/2010 07:48 PM, Jian Peng wrote:
> So it is reasonable to add extra check in ahci_start_engine() without returning status of ST bit. If so, here is my patch
>
> --- libahci.c.orig 2010-12-08 10:42:48.383976763 -0800
> +++ libahci.c 2010-12-08 10:45:17.495156944 -0800
> @@ -542,6 +542,13 @@
> {
> void __iomem *port_mmio = ahci_port_base(ap);
> u32 tmp;
> + u8 status = readl(port_mmio + PORT_TFDATA) & 0xFF;
> +
> + /* avoid race condition per spec (end of section 10.1.2) */
> + if (status & (ATA_BUSY | ATA_DRQ) ||
> + ahci_scr_read(&ap->link, SCR_STATUS, &tmp) ||
> + (tmp & 0x0f) != 0x03)
> + return;
>
> /* start DMA */
> tmp = readl(port_mmio + PORT_CMD);
Yes, it is reasonable but I want to see that it actually fixes
something. There are just too many controllers which use this path to
blindly apply the above change and given my previous explanation even
without the above change any ahci controller _should_ work fine.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-12-08 18:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 7:43 questions regarding possible violation of AHCI spec in AHCI driver Jian Peng
2010-12-08 1:54 ` Robert Hancock
2010-12-08 10:07 ` Tejun Heo
2010-12-08 18:14 ` Jian Peng
2010-12-08 18:24 ` Tejun Heo
2010-12-08 18:48 ` Jian Peng
2010-12-08 18:52 ` Tejun Heo [this message]
2010-12-08 19:49 ` Jian Peng
2010-12-08 19:55 ` Tejun Heo
2010-12-08 20:09 ` Jian Peng
2010-12-08 22:54 ` Tejun Heo
2010-12-09 1:30 ` Jian Peng
2011-01-11 18:09 ` Jian Peng
2011-01-11 18:23 ` Tejun Heo
2011-01-11 18:55 ` Jian Peng
2011-01-12 0:45 ` Harik
2011-01-12 0:51 ` Jian Peng
2011-01-19 0:51 ` Jeff Garzik
2011-01-19 0:58 ` Jian Peng
2011-01-19 23:35 ` Jian Peng
2011-01-19 23:37 ` Jian Peng
2011-04-19 21:48 ` Jian Peng
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=4CFFD3EB.10800@kernel.org \
--to=tj@kernel.org \
--cc=hancockrwd@gmail.com \
--cc=jgarzik@pobox.com \
--cc=jipeng@broadcom.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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