From: Cort Dougan <cort@fsmlabs.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org
Subject: Re: Question about IRQ_PENDING/IRQ_REPLAY
Date: Sat, 3 Mar 2001 14:48:56 -0700 [thread overview]
Message-ID: <20010303144856.A18389@ftsoj.fsmlabs.com> (raw)
In-Reply-To: <19350126005232.15154@mailhost.mipsys.com> <Pine.LNX.4.10.10103030954060.17574-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10103030954060.17574-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Sat, Mar 03, 2001 at 10:00:53AM -0800
} > I don't have a simple way on PPC to cause the interrupt to happen again,
} > as you can imagine this is rather controller-specific. However, looking
} > at the code closely, I couldn't figure out a case where having
} > IRQ_PENDING in enable_irq() makes sense.
}
} It only makes sense for broken irq controllers. And most aren't. You can
} likely ignore it - and note how even on an x86, most of the irq controller
} code _does_ ignore it.
We do have broken interrupt controllers in this respect. We already have a
way of handling it. Ben, take a look at set_lost().
next prev parent reply other threads:[~2001-03-03 21:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 7:20 Question about IRQ_PENDING/IRQ_REPLAY Benjamin Herrenschmidt
2001-03-03 18:00 ` Linus Torvalds
2001-03-03 21:48 ` Cort Dougan [this message]
2001-03-04 21:06 ` Benjamin Herrenschmidt
2001-03-05 6:07 ` Cort Dougan
2001-03-05 9:48 ` Benjamin Herrenschmidt
2001-03-05 10:00 ` Benjamin Herrenschmidt
2001-03-05 18:15 ` Linus Torvalds
2001-03-05 21:00 ` Cort Dougan
2001-03-05 21:47 ` Benjamin Herrenschmidt
2001-03-05 21:39 ` Benjamin Herrenschmidt
2001-03-04 12:36 ` Benjamin Herrenschmidt
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=20010303144856.A18389@ftsoj.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox