From: Jeff Garzik <jgarzik@pobox.com>
To: shane.huang@amd.com
Cc: tj@kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH #upstream, v3] ahci: Implement SATA AHCI FIS-based switching support
Date: Thu, 03 Dec 2009 12:42:05 -0500 [thread overview]
Message-ID: <4B17F86D.1080805@pobox.com> (raw)
In-Reply-To: <1252402105.3514.7.camel@zm-desktop>
On 09/08/2009 05:28 AM, Shane Huang wrote:
> Implement SATA AHCI FIS-based switching support.
>
> Tested on AMD internal reference board.
>
> Signed-off-by: Shane Huang<shane.huang@amd.com>
> Cc: Tejun Heo<tj@kernel.org>
> ---
> Changes from the last version(v2):
> * Move fbs_need_dec from struct ahci_port_priv to ahci_error_intr() as
> a local variable.
> * Add BUG_ON(!pp->fbs_enabled) for ahci_fbs_dec_intr().
> * Refine the retry loop in ahci_fbs_dec_intr().
> * Refine the code to determine failed active link with ap->pmp_link in
> ahci_error_intr().
> * WARN_ON() in ahci_port_intr() can storm the machine with consecutive
> stack dumps, replace it with WARN_ON_ONCE().
> * Refine ahci_enable_fbs()/ahci_disable_fbs(), and discard the message
> for controllers which do not support FBS.
> * Add a warning message in ahci_port_start() for those weird controllers
> which support CAP.FBSS but do not support PxCMD.FBSCP.
> * Several small corrections for better coding style.
>
> drivers/ata/ahci.c | 225 +++++++++++++++++++++++++++++++++++++++++++++++-----
> 1 files changed, 206 insertions(+), 19 deletions(-)
OK, I'm ready to get back to this... Would you please resubmit this
patch, rediff'd for the current upstream kernel?
I will queue it for kernel 2.6.34, because it needs plenty of testing --
both for FBS-enabled AHCI, and to be sure we don't break non-FBS AHCI.
Jeff
next prev parent reply other threads:[~2009-12-03 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 9:28 [PATCH #upstream, v3] ahci: Implement SATA AHCI FIS-based switching support Shane Huang
2009-09-14 15:01 ` Tejun Heo
2009-12-03 17:42 ` Jeff Garzik [this message]
2009-12-04 4:39 ` Huang, Shane
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=4B17F86D.1080805@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=shane.huang@amd.com \
--cc=tj@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).