linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: albertl@mail.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 18:10:51 +0900	[thread overview]
Message-ID: <4416889B.1060601@gmail.com> (raw)
In-Reply-To: <44166BDF.4000702@pobox.com>

Jeff Garzik wrote:
> Tejun Heo wrote:
> 
>> 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.
> 
> 
> Except for the HSM, there is no guaranteed way to know if an interrupt 
> is spurious or not on many controllers, who lack an "I have an 
> interrupt" bit.
> 

What I'm thinking is to disable interrupt (hopefully using controller 
flag, maybe PCI IRQ disable, ATA_NIEN if nothing else is possible) on 
error condition which may breach HSM and force controller and device to 
a known state in ->error_handler() or ->post_internal_command() before 
reenabling interrupt. This method will also make libata resistant to 
screaming IRQ cases some controllers/drives show under certain 
circumstances.

And I think clearing ->hsm_task_state belongs to (to-be-added) 
->post_internal_command() as it belongs to ->eng_timeout but not to EH 
framework.

Thanks.

-- 
tejun

  reply	other threads:[~2006-03-14  9:11 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
2006-03-14  7:08   ` Jeff Garzik
2006-03-14  9:10     ` Tejun Heo [this message]
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=4416889B.1060601@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).