From: Tejun Heo <htejun@gmail.com>
To: albertl@mail.com
Cc: Jeff Garzik <jgarzik@pobox.com>, IDE Linux <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 1/1] libata-dev: add flush task to ata_exec_internal()
Date: Tue, 14 Mar 2006 15:12:44 +0900 [thread overview]
Message-ID: <44165EDC.3070800@gmail.com> (raw)
In-Reply-To: <44163628.2000001@tw.ibm.com>
Albert Lee wrote:
> Add ata_port_flush_task() to ata_exec_internal().
>
> Signed-off-by: Albert Lee <albertcc@tw.ibm.com>
> ---
>
> It seems we also need ata_port_flush_task() in ata_exec_internal().
>
> Patch against the upstream branch
> (fb21f0d0ec7e31cc814165e1a9d2662d9c9dd980).
>
> For your review, thanks,
>
> Albert
>
> --- upstream0/drivers/scsi/libata-core.c 2006-03-14 10:31:01.000000000 +0800
> +++ exec_internal/drivers/scsi/libata-core.c 2006-03-14 10:55:24.000000000 +0800
> @@ -962,6 +962,8 @@ ata_exec_internal(struct ata_port *ap, s
> spin_unlock_irqrestore(&ap->host_set->lock, flags);
>
> if (!wait_for_completion_timeout(&wait, ATA_TMOUT_INTERNAL)) {
> + ata_port_flush_task(ap);
> +
> spin_lock_irqsave(&ap->host_set->lock, flags);
>
> /* We're racing with irq here. If we lose, the
>
Yes, we certainly need this. The irq handling isn't really correct
either as irq handlers don't clear interrupt conditions on spurious
interrupts. I hope/plan to address this during EH work.
Anyways, ACK.
Thanks.
--
tejun
next prev parent reply other threads:[~2006-03-14 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 3:19 [PATCH 1/1] libata-dev: add flush task to ata_exec_internal() Albert Lee
2006-03-14 6:12 ` Tejun Heo [this message]
2006-03-14 7:08 ` Jeff Garzik
2006-03-14 9:10 ` Tejun Heo
2006-03-22 1:40 ` Jeff Garzik
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=44165EDC.3070800@gmail.com \
--to=htejun@gmail.com \
--cc=albertl@mail.com \
--cc=jgarzik@pobox.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).