From: Andrew Morton <akpm@linux-foundation.org>
To: Bernhard Walle <bwalle@suse.de>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] Fix irqpoll on IA64 (timer interrupt != 0)
Date: Thu, 22 Mar 2007 21:09:22 +0000 [thread overview]
Message-ID: <20070322140922.a59bea5c.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070320150027.GA18143@strauss.suse.de>
On Tue, 20 Mar 2007 16:00:27 +0100
Bernhard Walle <bwalle@suse.de> wrote:
> On IA64, the timer interrupt is not (always?) zero as it is on x86 platforms.
> Also, the timer interrupt is CPU-local. Two things need to be changed to make
> the irqpoll option make also working on IA64:
>
> o Call note_interrupt() also on CPU-local interrupts in __do_IRQ().
> o Set a variable timer_irq to the value of the timer interrupt
> after the timer interrupt has been registered and assigned.
>
> That requires changes in Linux-generic files. The default of timer_irq is 0, so
> the patch doesn't break i386/x86_64. However, other platforms also may also
> have a timer interrupt non-equal to zero, so they can also use the new
> set_timer_interrupt() function.
Couple of things..
I think the term 'timer_interrupt' is a bit generic-sounding. Would it be
better to call it irqpoll_interrupt? After all, some architecture might
want to use, umm, the keyboard interrupt to trigger IRQ polling ;)
Also, the code presently passes the magic IRQ number into the generic IRQ
code. I wonder if we'd get a more pleasing result if we were to make the
generic IRQ code call _out_ to the architecture:
diff -puN kernel/irq/spurious.c~a kernel/irq/spurious.c
--- a/kernel/irq/spurious.c~a
+++ a/kernel/irq/spurious.c
@@ -135,6 +135,11 @@ report_bad_irq(unsigned int irq, struct
}
}
+bool __attribute__((weak)) arch_is_irqpoll_irq(unsigned int irq)
+{
+ return false;
+}
+
void note_interrupt(unsigned int irq, struct irq_desc *desc,
irqreturn_t action_ret)
{
@@ -146,7 +151,8 @@ void note_interrupt(unsigned int irq, st
if (unlikely(irqfixup)) {
/* Don't punish working computers */
- if ((irqfixup = 2 && irq = 0) || action_ret = IRQ_NONE) {
+ if ((irqfixup = 2 && arch_is_irqpoll_irq(irq)) ||
+ action_ret = IRQ_NONE) {
int ok = misrouted_irq(irq);
if (action_ret = IRQ_NONE)
desc->irqs_unhandled -= ok;
diff -puN include/linux/irq.h~a include/linux/irq.h
--- a/include/linux/irq.h~a
+++ a/include/linux/irq.h
@@ -314,6 +314,7 @@ static inline void generic_handle_irq(un
/* Handling of unhandled and spurious interrupts: */
extern void note_interrupt(unsigned int irq, struct irq_desc *desc,
int action_ret);
+extern bool arch_is_irqpoll_irq(unsigned int irq);
/* Resending of interrupts :*/
void check_irq_resend(struct irq_desc *desc, unsigned int irq);
_
Then, ia64 can implement arch_is_irqpoll_irq() and it can do whatever it
wants in there.
The __attribute__((weak)) thing adds a little bit of overhead, but I don't
think this is a fastpath?
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Bernhard Walle <bwalle@suse.de>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] Fix irqpoll on IA64 (timer interrupt != 0)
Date: Thu, 22 Mar 2007 14:09:22 -0700 [thread overview]
Message-ID: <20070322140922.a59bea5c.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070320150027.GA18143@strauss.suse.de>
On Tue, 20 Mar 2007 16:00:27 +0100
Bernhard Walle <bwalle@suse.de> wrote:
> On IA64, the timer interrupt is not (always?) zero as it is on x86 platforms.
> Also, the timer interrupt is CPU-local. Two things need to be changed to make
> the irqpoll option make also working on IA64:
>
> o Call note_interrupt() also on CPU-local interrupts in __do_IRQ().
> o Set a variable timer_irq to the value of the timer interrupt
> after the timer interrupt has been registered and assigned.
>
> That requires changes in Linux-generic files. The default of timer_irq is 0, so
> the patch doesn't break i386/x86_64. However, other platforms also may also
> have a timer interrupt non-equal to zero, so they can also use the new
> set_timer_interrupt() function.
Couple of things..
I think the term 'timer_interrupt' is a bit generic-sounding. Would it be
better to call it irqpoll_interrupt? After all, some architecture might
want to use, umm, the keyboard interrupt to trigger IRQ polling ;)
Also, the code presently passes the magic IRQ number into the generic IRQ
code. I wonder if we'd get a more pleasing result if we were to make the
generic IRQ code call _out_ to the architecture:
diff -puN kernel/irq/spurious.c~a kernel/irq/spurious.c
--- a/kernel/irq/spurious.c~a
+++ a/kernel/irq/spurious.c
@@ -135,6 +135,11 @@ report_bad_irq(unsigned int irq, struct
}
}
+bool __attribute__((weak)) arch_is_irqpoll_irq(unsigned int irq)
+{
+ return false;
+}
+
void note_interrupt(unsigned int irq, struct irq_desc *desc,
irqreturn_t action_ret)
{
@@ -146,7 +151,8 @@ void note_interrupt(unsigned int irq, st
if (unlikely(irqfixup)) {
/* Don't punish working computers */
- if ((irqfixup == 2 && irq == 0) || action_ret == IRQ_NONE) {
+ if ((irqfixup == 2 && arch_is_irqpoll_irq(irq)) ||
+ action_ret == IRQ_NONE) {
int ok = misrouted_irq(irq);
if (action_ret == IRQ_NONE)
desc->irqs_unhandled -= ok;
diff -puN include/linux/irq.h~a include/linux/irq.h
--- a/include/linux/irq.h~a
+++ a/include/linux/irq.h
@@ -314,6 +314,7 @@ static inline void generic_handle_irq(un
/* Handling of unhandled and spurious interrupts: */
extern void note_interrupt(unsigned int irq, struct irq_desc *desc,
int action_ret);
+extern bool arch_is_irqpoll_irq(unsigned int irq);
/* Resending of interrupts :*/
void check_irq_resend(struct irq_desc *desc, unsigned int irq);
_
Then, ia64 can implement arch_is_irqpoll_irq() and it can do whatever it
wants in there.
The __attribute__((weak)) thing adds a little bit of overhead, but I don't
think this is a fastpath?
next prev parent reply other threads:[~2007-03-22 21:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 14:59 [PATCH] Fix irqpoll on IA64 (timer interrupt != 0) Bernhard Walle
2007-03-20 15:00 ` Bernhard Walle
2007-03-22 21:09 ` Andrew Morton [this message]
2007-03-22 21:09 ` Andrew Morton
2007-03-22 21:23 ` Thomas Gleixner
2007-03-22 21:23 ` Thomas Gleixner
2007-03-22 22:02 ` Andrew Morton
2007-03-22 22:02 ` Andrew Morton
2007-03-22 22:45 ` Bernhard Walle
2007-03-22 22:45 ` Bernhard Walle
2007-03-22 23:04 ` Bernhard Walle
2007-03-22 23:04 ` Bernhard Walle
2007-03-22 23:15 ` Andrew Morton
2007-03-22 23:15 ` Andrew Morton
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=20070322140922.a59bea5c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bwalle@suse.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.