All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nathan Bryant <nbryant@optonline.net>
Cc: Chris Wedgwood <cw@f00f.org>,
	William Lee Irwin III <wli@holomorphy.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] i386 reduce spurious interrupt noise
Date: Thu, 02 Sep 2004 20:27:28 +0100	[thread overview]
Message-ID: <1094153248.5809.41.camel@localhost.localdomain> (raw)
In-Reply-To: <41377EF6.4010902@optonline.net>

On Iau, 2004-09-02 at 21:13, Nathan Bryant wrote:
> Right, spurious interrupts aren't a big deal on i386. They happen now 
> and then with some devices because some hardware timing tolerances are a 
> little too tight. 

It also happens on a lot of hardware on the odd instance a non IRQ code
path clears down an interrupt just as its being raised. IDE does it now
and then for example.


  reply	other threads:[~2004-09-02 20:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 19:28 [PATCH] i386 reduce spurious interrupt noise Chris Wedgwood
2004-09-02 19:34 ` William Lee Irwin III
2004-09-02 19:47   ` Chris Wedgwood
2004-09-02 19:52     ` William Lee Irwin III
2004-09-02 19:59       ` Chris Wedgwood
2004-09-02 20:13     ` Nathan Bryant
2004-09-02 19:27       ` Alan Cox [this message]
2004-09-02 20:32         ` Chris Wedgwood
2004-09-10 21:23 ` Maciej W. Rozycki
2004-09-10 23:10   ` Chris Wedgwood
2004-09-10 22:21     ` Alan Cox
2004-09-10 23:28       ` Chris Wedgwood
2004-09-11 13:36         ` Alan Cox
2004-09-11  0:14     ` Maciej W. Rozycki
2004-09-11  0:17       ` Chris Wedgwood
2004-09-11  0:33         ` Maciej W. Rozycki

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=1094153248.5809.41.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbryant@optonline.net \
    --cc=torvalds@osdl.org \
    --cc=wli@holomorphy.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.