public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <teheo@suse.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>, Greg KH <gregkh@suse.de>
Subject: Re: [GIT PULL tip/genirq] Please pull from lost-spurious-irq
Date: Tue, 03 Aug 2010 12:15:52 +0200	[thread overview]
Message-ID: <4C57EC58.4020301@suse.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1008031205040.3225@localhost.localdomain>

Hello,

On 08/03/2010 12:06 PM, Thomas Gleixner wrote:
>> These problems do happen on intel chipset machines and is something
>> which can be worked around with some effort.  Eh, let's talk on the
>> other reply.
> 
> So you're saying that the ATA problem is restricted to Intel chipsets?
> Do we know the root cause ?

The original sentence is missing an 'also'.  Severals have been root
caused and worked around.  For SATA, one of the notable problems was
misinterpretation of nIEN (interrupt block bit on the ATA device side)
on both device and host sides.  In traditional IDE API, the interrupt
bit is primarily under the control of the device, so it's pretty
difficult to guarantee reliable operation from driver side only.  For
PATA, the device actually has full control of the interrupt line, so
it's much worse.

Thanks.

-- 
tejun

  reply	other threads:[~2010-08-03 10:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 13:42 [GIT PULL tip/genirq] Please pull from lost-spurious-irq Tejun Heo
2010-07-28 13:46 ` Tejun Heo
2010-07-29  8:44   ` Thomas Gleixner
2010-07-30  9:46     ` Tejun Heo
2010-08-02 14:07       ` Thomas Gleixner
2010-08-02 15:28         ` Tejun Heo
2010-08-02 15:35           ` Tejun Heo
2010-08-02 18:52             ` Thomas Gleixner
2010-08-02 19:57               ` Tejun Heo
2010-08-03 10:06                 ` Thomas Gleixner
2010-08-03 10:15                   ` Tejun Heo [this message]
2010-08-02 21:06               ` Tejun Heo
2010-08-02 21:51                 ` Thomas Gleixner
2010-08-02 17:10           ` Thomas Gleixner
2010-08-02 20:48             ` Tejun Heo
2010-08-02 22:28               ` Thomas Gleixner
2010-08-03  8:49                 ` Tejun Heo
2010-08-03 11:43                   ` Thomas Gleixner

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=4C57EC58.4020301@suse.de \
    --to=teheo@suse.de \
    --cc=gregkh@suse.de \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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