From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <torvalds@transmeta.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Question about IRQ_PENDING/IRQ_REPLAY
Date: Mon, 5 Mar 2001 22:39:49 +0100 [thread overview]
Message-ID: <19350128151133.7893@smtp.wanadoo.fr> (raw)
In-Reply-To: <980l3v$7ct$1@penguin.transmeta.com>
In-Reply-To: <980l3v$7ct$1@penguin.transmeta.com>
>And I seriously doubt that PPC SMP irq handling has gotten _nearly_ the
>amount of testing and hard work that the x86 counterpart has. Things
>like support for CPU affinity, per-irq spinlocks, etc etc.
Some of those are the reason I moved part of the x86 irq.c code to PPC
indeed.
>Now, I'm not saying that irq.c would necessarily work as-is. It probably
>doesn't support all the things that other architectures might need (but
>with three completely different irq controllers on just standard PCs
>alone, I bet it supports most of it), and I know ia64 wants to extend it
>to be more spread out over different CPU's, but most of the high-level
>stuff probably _can_ and should be fairly common.
And I think they are. One thing is that if made "common", do_IRQ have to
be split into an arch-specific function that retrives the irq_number (and
does the ack on some controller), and the actual "dispatch" function that
does all the flags game and calls the handler.
I've slightly extended it using the IRQ_PERCPU flag to prevent IRQ_INPROGRESS
from ever beeing set (a bit hackish but I wanted that for IPIs since they
use ordinary irq_desc structures for us in most cases).
Ben.
next prev parent reply other threads:[~2001-03-05 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
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 [this message]
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=19350128151133.7893@smtp.wanadoo.fr \
--to=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