2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* linux/kernel/irq/handle.c
|
|
|
|
*
|
2006-06-29 09:24:50 +00:00
|
|
|
* Copyright (C) 1992, 1998-2006 Linus Torvalds, Ingo Molnar
|
|
|
|
* Copyright (C) 2005-2006, Thomas Gleixner, Russell King
|
2005-04-16 22:20:36 +00:00
|
|
|
*
|
|
|
|
* This file contains the core interrupt handling code.
|
2006-06-29 09:24:50 +00:00
|
|
|
*
|
|
|
|
* Detailed information is available in Documentation/DocBook/genericirq
|
|
|
|
*
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/irq.h>
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/random.h>
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <linux/kernel_stat.h>
|
|
|
|
|
|
|
|
#include "internals.h"
|
|
|
|
|
2006-06-29 09:24:51 +00:00
|
|
|
/**
|
|
|
|
* handle_bad_irq - handle spurious and unhandled irqs
|
2006-09-01 04:27:44 +00:00
|
|
|
* @irq: the interrupt number
|
|
|
|
* @desc: description of the interrupt
|
|
|
|
*
|
|
|
|
* Handles spurious and unhandled IRQ's. It also prints a debugmessage.
|
2006-06-29 09:24:51 +00:00
|
|
|
*/
|
2008-10-15 13:27:23 +00:00
|
|
|
void handle_bad_irq(unsigned int irq, struct irq_desc *desc)
|
2006-06-29 09:24:51 +00:00
|
|
|
{
|
2006-06-29 09:24:58 +00:00
|
|
|
print_irq_desc(irq, desc);
|
2008-10-15 13:27:23 +00:00
|
|
|
kstat_incr_irqs_this_cpu(irq, desc);
|
2006-06-29 09:24:51 +00:00
|
|
|
ack_bad_irq(irq);
|
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* Linux has a controller-independent interrupt architecture.
|
|
|
|
* Every controller has a 'controller-template', that is used
|
|
|
|
* by the main code to do the right thing. Each driver-visible
|
2006-06-29 09:24:40 +00:00
|
|
|
* interrupt source is transparently wired to the appropriate
|
2005-04-16 22:20:36 +00:00
|
|
|
* controller. Thus drivers need not be aware of the
|
|
|
|
* interrupt-controller.
|
|
|
|
*
|
|
|
|
* The code is designed to be easily extended with new/different
|
|
|
|
* interrupt controllers, without having to do assembly magic or
|
|
|
|
* having to touch the generic code.
|
|
|
|
*
|
|
|
|
* Controller mappings for all interrupt sources:
|
|
|
|
*/
|
2008-08-20 03:49:47 +00:00
|
|
|
int nr_irqs = NR_IRQS;
|
2008-08-20 03:50:30 +00:00
|
|
|
EXPORT_SYMBOL_GPL(nr_irqs);
|
2008-08-20 03:50:00 +00:00
|
|
|
|
2007-05-08 07:29:13 +00:00
|
|
|
struct irq_desc irq_desc[NR_IRQS] __cacheline_aligned_in_smp = {
|
2005-04-16 22:20:36 +00:00
|
|
|
[0 ... NR_IRQS-1] = {
|
2005-05-17 04:53:43 +00:00
|
|
|
.status = IRQ_DISABLED,
|
2006-06-29 09:24:57 +00:00
|
|
|
.chip = &no_irq_chip,
|
2006-06-29 09:24:54 +00:00
|
|
|
.handle_irq = handle_bad_irq,
|
2006-06-29 09:24:50 +00:00
|
|
|
.depth = 1,
|
2008-09-25 02:04:35 +00:00
|
|
|
.lock = __SPIN_LOCK_UNLOCKED(irq_desc->lock),
|
2006-06-29 09:24:38 +00:00
|
|
|
#ifdef CONFIG_SMP
|
|
|
|
.affinity = CPU_MASK_ALL
|
|
|
|
#endif
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
};
|
2008-08-20 03:50:05 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
2006-06-29 09:24:46 +00:00
|
|
|
* What should we do if we get a hw irq event on an illegal vector?
|
|
|
|
* Each architecture has to answer this themself.
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
2006-06-29 09:24:46 +00:00
|
|
|
static void ack_bad(unsigned int irq)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2008-08-20 03:50:05 +00:00
|
|
|
struct irq_desc *desc;
|
|
|
|
|
|
|
|
desc = irq_to_desc(irq);
|
|
|
|
print_irq_desc(irq, desc);
|
2005-04-16 22:20:36 +00:00
|
|
|
ack_bad_irq(irq);
|
|
|
|
}
|
|
|
|
|
2006-06-29 09:24:46 +00:00
|
|
|
/*
|
|
|
|
* NOP functions
|
|
|
|
*/
|
|
|
|
static void noop(unsigned int irq)
|
|
|
|
{
|
|
|
|
}
|
|
|
|
|
|
|
|
static unsigned int noop_ret(unsigned int irq)
|
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Generic no controller implementation
|
|
|
|
*/
|
2006-06-29 09:24:57 +00:00
|
|
|
struct irq_chip no_irq_chip = {
|
|
|
|
.name = "none",
|
2006-06-29 09:24:46 +00:00
|
|
|
.startup = noop_ret,
|
|
|
|
.shutdown = noop,
|
|
|
|
.enable = noop,
|
|
|
|
.disable = noop,
|
|
|
|
.ack = ack_bad,
|
|
|
|
.end = noop,
|
2005-04-16 22:20:36 +00:00
|
|
|
};
|
|
|
|
|
2006-07-01 21:30:08 +00:00
|
|
|
/*
|
|
|
|
* Generic dummy implementation which can be used for
|
|
|
|
* real dumb interrupt sources
|
|
|
|
*/
|
|
|
|
struct irq_chip dummy_irq_chip = {
|
|
|
|
.name = "dummy",
|
|
|
|
.startup = noop_ret,
|
|
|
|
.shutdown = noop,
|
|
|
|
.enable = noop,
|
|
|
|
.disable = noop,
|
|
|
|
.ack = noop,
|
|
|
|
.mask = noop,
|
|
|
|
.unmask = noop,
|
|
|
|
.end = noop,
|
|
|
|
};
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* Special, empty irq handler:
|
|
|
|
*/
|
IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
of passing regs around manually through all ~1800 interrupt handlers in the
Linux kernel.
The regs pointer is used in few places, but it potentially costs both stack
space and code to pass it around. On the FRV arch, removing the regs parameter
from all the genirq function results in a 20% speed up of the IRQ exit path
(ie: from leaving timer_interrupt() to leaving do_IRQ()).
Where appropriate, an arch may override the generic storage facility and do
something different with the variable. On FRV, for instance, the address is
maintained in GR28 at all times inside the kernel as part of general exception
handling.
Having looked over the code, it appears that the parameter may be handed down
through up to twenty or so layers of functions. Consider a USB character
device attached to a USB hub, attached to a USB controller that posts its
interrupts through a cascaded auxiliary interrupt controller. A character
device driver may want to pass regs to the sysrq handler through the input
layer which adds another few layers of parameter passing.
I've build this code with allyesconfig for x86_64 and i386. I've runtested the
main part of the code on FRV and i386, though I can't test most of the drivers.
I've also done partial conversion for powerpc and MIPS - these at least compile
with minimal configurations.
This will affect all archs. Mostly the changes should be relatively easy.
Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
struct pt_regs *old_regs = set_irq_regs(regs);
And put the old one back at the end:
set_irq_regs(old_regs);
Don't pass regs through to generic_handle_irq() or __do_IRQ().
In timer_interrupt(), this sort of change will be necessary:
- update_process_times(user_mode(regs));
- profile_tick(CPU_PROFILING, regs);
+ update_process_times(user_mode(get_irq_regs()));
+ profile_tick(CPU_PROFILING);
I'd like to move update_process_times()'s use of get_irq_regs() into itself,
except that i386, alone of the archs, uses something other than user_mode().
Some notes on the interrupt handling in the drivers:
(*) input_dev() is now gone entirely. The regs pointer is no longer stored in
the input_dev struct.
(*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
something different depending on whether it's been supplied with a regs
pointer or not.
(*) Various IRQ handler function pointers have been moved to type
irq_handler_t.
Signed-Off-By: David Howells <dhowells@redhat.com>
(cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
2006-10-05 13:55:46 +00:00
|
|
|
irqreturn_t no_action(int cpl, void *dev_id)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
|
|
|
return IRQ_NONE;
|
|
|
|
}
|
|
|
|
|
2006-06-29 09:24:46 +00:00
|
|
|
/**
|
|
|
|
* handle_IRQ_event - irq action chain handler
|
|
|
|
* @irq: the interrupt number
|
|
|
|
* @action: the interrupt action chain for this irq
|
|
|
|
*
|
|
|
|
* Handles the action chain of an irq event
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
of passing regs around manually through all ~1800 interrupt handlers in the
Linux kernel.
The regs pointer is used in few places, but it potentially costs both stack
space and code to pass it around. On the FRV arch, removing the regs parameter
from all the genirq function results in a 20% speed up of the IRQ exit path
(ie: from leaving timer_interrupt() to leaving do_IRQ()).
Where appropriate, an arch may override the generic storage facility and do
something different with the variable. On FRV, for instance, the address is
maintained in GR28 at all times inside the kernel as part of general exception
handling.
Having looked over the code, it appears that the parameter may be handed down
through up to twenty or so layers of functions. Consider a USB character
device attached to a USB hub, attached to a USB controller that posts its
interrupts through a cascaded auxiliary interrupt controller. A character
device driver may want to pass regs to the sysrq handler through the input
layer which adds another few layers of parameter passing.
I've build this code with allyesconfig for x86_64 and i386. I've runtested the
main part of the code on FRV and i386, though I can't test most of the drivers.
I've also done partial conversion for powerpc and MIPS - these at least compile
with minimal configurations.
This will affect all archs. Mostly the changes should be relatively easy.
Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
struct pt_regs *old_regs = set_irq_regs(regs);
And put the old one back at the end:
set_irq_regs(old_regs);
Don't pass regs through to generic_handle_irq() or __do_IRQ().
In timer_interrupt(), this sort of change will be necessary:
- update_process_times(user_mode(regs));
- profile_tick(CPU_PROFILING, regs);
+ update_process_times(user_mode(get_irq_regs()));
+ profile_tick(CPU_PROFILING);
I'd like to move update_process_times()'s use of get_irq_regs() into itself,
except that i386, alone of the archs, uses something other than user_mode().
Some notes on the interrupt handling in the drivers:
(*) input_dev() is now gone entirely. The regs pointer is no longer stored in
the input_dev struct.
(*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
something different depending on whether it's been supplied with a regs
pointer or not.
(*) Various IRQ handler function pointers have been moved to type
irq_handler_t.
Signed-Off-By: David Howells <dhowells@redhat.com>
(cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
2006-10-05 13:55:46 +00:00
|
|
|
irqreturn_t handle_IRQ_event(unsigned int irq, struct irqaction *action)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2006-06-23 09:06:00 +00:00
|
|
|
irqreturn_t ret, retval = IRQ_NONE;
|
|
|
|
unsigned int status = 0;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-07-02 02:29:31 +00:00
|
|
|
if (!(action->flags & IRQF_DISABLED))
|
2006-07-03 07:25:25 +00:00
|
|
|
local_irq_enable_in_hardirq();
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
do {
|
IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
of passing regs around manually through all ~1800 interrupt handlers in the
Linux kernel.
The regs pointer is used in few places, but it potentially costs both stack
space and code to pass it around. On the FRV arch, removing the regs parameter
from all the genirq function results in a 20% speed up of the IRQ exit path
(ie: from leaving timer_interrupt() to leaving do_IRQ()).
Where appropriate, an arch may override the generic storage facility and do
something different with the variable. On FRV, for instance, the address is
maintained in GR28 at all times inside the kernel as part of general exception
handling.
Having looked over the code, it appears that the parameter may be handed down
through up to twenty or so layers of functions. Consider a USB character
device attached to a USB hub, attached to a USB controller that posts its
interrupts through a cascaded auxiliary interrupt controller. A character
device driver may want to pass regs to the sysrq handler through the input
layer which adds another few layers of parameter passing.
I've build this code with allyesconfig for x86_64 and i386. I've runtested the
main part of the code on FRV and i386, though I can't test most of the drivers.
I've also done partial conversion for powerpc and MIPS - these at least compile
with minimal configurations.
This will affect all archs. Mostly the changes should be relatively easy.
Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
struct pt_regs *old_regs = set_irq_regs(regs);
And put the old one back at the end:
set_irq_regs(old_regs);
Don't pass regs through to generic_handle_irq() or __do_IRQ().
In timer_interrupt(), this sort of change will be necessary:
- update_process_times(user_mode(regs));
- profile_tick(CPU_PROFILING, regs);
+ update_process_times(user_mode(get_irq_regs()));
+ profile_tick(CPU_PROFILING);
I'd like to move update_process_times()'s use of get_irq_regs() into itself,
except that i386, alone of the archs, uses something other than user_mode().
Some notes on the interrupt handling in the drivers:
(*) input_dev() is now gone entirely. The regs pointer is no longer stored in
the input_dev struct.
(*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
something different depending on whether it's been supplied with a regs
pointer or not.
(*) Various IRQ handler function pointers have been moved to type
irq_handler_t.
Signed-Off-By: David Howells <dhowells@redhat.com>
(cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
2006-10-05 13:55:46 +00:00
|
|
|
ret = action->handler(irq, action->dev_id);
|
2005-04-16 22:20:36 +00:00
|
|
|
if (ret == IRQ_HANDLED)
|
|
|
|
status |= action->flags;
|
|
|
|
retval |= ret;
|
|
|
|
action = action->next;
|
|
|
|
} while (action);
|
|
|
|
|
2006-07-02 02:29:31 +00:00
|
|
|
if (status & IRQF_SAMPLE_RANDOM)
|
2005-04-16 22:20:36 +00:00
|
|
|
add_interrupt_randomness(irq);
|
|
|
|
local_irq_disable();
|
|
|
|
|
|
|
|
return retval;
|
|
|
|
}
|
|
|
|
|
2006-09-26 06:32:07 +00:00
|
|
|
#ifndef CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ
|
2006-06-29 09:24:46 +00:00
|
|
|
/**
|
|
|
|
* __do_IRQ - original all in one highlevel IRQ handler
|
|
|
|
* @irq: the interrupt number
|
|
|
|
*
|
|
|
|
* __do_IRQ handles all normal device IRQ's (the special
|
2005-04-16 22:20:36 +00:00
|
|
|
* SMP cross-CPU interrupts have their own specific
|
|
|
|
* handlers).
|
2006-06-29 09:24:46 +00:00
|
|
|
*
|
|
|
|
* This is the original x86 implementation which is used for every
|
|
|
|
* interrupt type.
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
2008-02-08 12:19:53 +00:00
|
|
|
unsigned int __do_IRQ(unsigned int irq)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2008-08-20 03:50:05 +00:00
|
|
|
struct irq_desc *desc = irq_to_desc(irq);
|
2006-06-29 09:24:40 +00:00
|
|
|
struct irqaction *action;
|
2005-04-16 22:20:36 +00:00
|
|
|
unsigned int status;
|
|
|
|
|
2008-10-15 13:27:23 +00:00
|
|
|
kstat_incr_irqs_this_cpu(irq, desc);
|
|
|
|
|
2005-09-06 22:17:25 +00:00
|
|
|
if (CHECK_IRQ_PER_CPU(desc->status)) {
|
2005-04-16 22:20:36 +00:00
|
|
|
irqreturn_t action_ret;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* No locking required for CPU-local interrupts:
|
|
|
|
*/
|
[PATCH] genirq: rename desc->handler to desc->chip
This patch-queue improves the generic IRQ layer to be truly generic, by adding
various abstractions and features to it, without impacting existing
functionality.
While the queue can be best described as "fix and improve everything in the
generic IRQ layer that we could think of", and thus it consists of many
smaller features and lots of cleanups, the one feature that stands out most is
the new 'irq chip' abstraction.
The irq-chip abstraction is about describing and coding and IRQ controller
driver by mapping its raw hardware capabilities [and quirks, if needed] in a
straightforward way, without having to think about "IRQ flow"
(level/edge/etc.) type of details.
This stands in contrast with the current 'irq-type' model of genirq
architectures, which 'mixes' raw hardware capabilities with 'flow' details.
The patchset supports both types of irq controller designs at once, and
converts i386 and x86_64 to the new irq-chip design.
As a bonus side-effect of the irq-chip approach, chained interrupt controllers
(master/slave PIC constructs, etc.) are now supported by design as well.
The end result of this patchset intends to be simpler architecture-level code
and more consolidation between architectures.
We reused many bits of code and many concepts from Russell King's ARM IRQ
layer, the merging of which was one of the motivations for this patchset.
This patch:
rename desc->handler to desc->chip.
Originally i did not want to do this, because it's a big patch. But having
both "desc->handler", "desc->handle_irq" and "action->handler" caused a
large degree of confusion and made the code appear alot less clean than it
truly is.
I have also attempted a dual approach as well by introducing a
desc->chip alias - but that just wasnt robust enough and broke
frequently.
So lets get over with this quickly. The conversion was done automatically
via scripts and converts all the code in the kernel.
This renaming patch is the first one amongst the patches, so that the
remaining patches can stay flexible and can be merged and split up
without having some big monolithic patch act as a merge barrier.
[akpm@osdl.org: build fix]
[akpm@osdl.org: another build fix]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-06-29 09:24:36 +00:00
|
|
|
if (desc->chip->ack)
|
|
|
|
desc->chip->ack(irq);
|
2007-11-15 01:00:15 +00:00
|
|
|
if (likely(!(desc->status & IRQ_DISABLED))) {
|
|
|
|
action_ret = handle_IRQ_event(irq, desc->action);
|
|
|
|
if (!noirqdebug)
|
|
|
|
note_interrupt(irq, desc, action_ret);
|
|
|
|
}
|
[PATCH] genirq: rename desc->handler to desc->chip
This patch-queue improves the generic IRQ layer to be truly generic, by adding
various abstractions and features to it, without impacting existing
functionality.
While the queue can be best described as "fix and improve everything in the
generic IRQ layer that we could think of", and thus it consists of many
smaller features and lots of cleanups, the one feature that stands out most is
the new 'irq chip' abstraction.
The irq-chip abstraction is about describing and coding and IRQ controller
driver by mapping its raw hardware capabilities [and quirks, if needed] in a
straightforward way, without having to think about "IRQ flow"
(level/edge/etc.) type of details.
This stands in contrast with the current 'irq-type' model of genirq
architectures, which 'mixes' raw hardware capabilities with 'flow' details.
The patchset supports both types of irq controller designs at once, and
converts i386 and x86_64 to the new irq-chip design.
As a bonus side-effect of the irq-chip approach, chained interrupt controllers
(master/slave PIC constructs, etc.) are now supported by design as well.
The end result of this patchset intends to be simpler architecture-level code
and more consolidation between architectures.
We reused many bits of code and many concepts from Russell King's ARM IRQ
layer, the merging of which was one of the motivations for this patchset.
This patch:
rename desc->handler to desc->chip.
Originally i did not want to do this, because it's a big patch. But having
both "desc->handler", "desc->handle_irq" and "action->handler" caused a
large degree of confusion and made the code appear alot less clean than it
truly is.
I have also attempted a dual approach as well by introducing a
desc->chip alias - but that just wasnt robust enough and broke
frequently.
So lets get over with this quickly. The conversion was done automatically
via scripts and converts all the code in the kernel.
This renaming patch is the first one amongst the patches, so that the
remaining patches can stay flexible and can be merged and split up
without having some big monolithic patch act as a merge barrier.
[akpm@osdl.org: build fix]
[akpm@osdl.org: another build fix]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-06-29 09:24:36 +00:00
|
|
|
desc->chip->end(irq);
|
2005-04-16 22:20:36 +00:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
spin_lock(&desc->lock);
|
[PATCH] genirq: rename desc->handler to desc->chip
This patch-queue improves the generic IRQ layer to be truly generic, by adding
various abstractions and features to it, without impacting existing
functionality.
While the queue can be best described as "fix and improve everything in the
generic IRQ layer that we could think of", and thus it consists of many
smaller features and lots of cleanups, the one feature that stands out most is
the new 'irq chip' abstraction.
The irq-chip abstraction is about describing and coding and IRQ controller
driver by mapping its raw hardware capabilities [and quirks, if needed] in a
straightforward way, without having to think about "IRQ flow"
(level/edge/etc.) type of details.
This stands in contrast with the current 'irq-type' model of genirq
architectures, which 'mixes' raw hardware capabilities with 'flow' details.
The patchset supports both types of irq controller designs at once, and
converts i386 and x86_64 to the new irq-chip design.
As a bonus side-effect of the irq-chip approach, chained interrupt controllers
(master/slave PIC constructs, etc.) are now supported by design as well.
The end result of this patchset intends to be simpler architecture-level code
and more consolidation between architectures.
We reused many bits of code and many concepts from Russell King's ARM IRQ
layer, the merging of which was one of the motivations for this patchset.
This patch:
rename desc->handler to desc->chip.
Originally i did not want to do this, because it's a big patch. But having
both "desc->handler", "desc->handle_irq" and "action->handler" caused a
large degree of confusion and made the code appear alot less clean than it
truly is.
I have also attempted a dual approach as well by introducing a
desc->chip alias - but that just wasnt robust enough and broke
frequently.
So lets get over with this quickly. The conversion was done automatically
via scripts and converts all the code in the kernel.
This renaming patch is the first one amongst the patches, so that the
remaining patches can stay flexible and can be merged and split up
without having some big monolithic patch act as a merge barrier.
[akpm@osdl.org: build fix]
[akpm@osdl.org: another build fix]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-06-29 09:24:36 +00:00
|
|
|
if (desc->chip->ack)
|
|
|
|
desc->chip->ack(irq);
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* REPLAY is when Linux resends an IRQ that was dropped earlier
|
|
|
|
* WAITING is used by probe to mark irqs that are being tested
|
|
|
|
*/
|
|
|
|
status = desc->status & ~(IRQ_REPLAY | IRQ_WAITING);
|
|
|
|
status |= IRQ_PENDING; /* we _want_ to handle it */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If the IRQ is disabled for whatever reason, we cannot
|
|
|
|
* use the action we have.
|
|
|
|
*/
|
|
|
|
action = NULL;
|
|
|
|
if (likely(!(status & (IRQ_DISABLED | IRQ_INPROGRESS)))) {
|
|
|
|
action = desc->action;
|
|
|
|
status &= ~IRQ_PENDING; /* we commit to handling */
|
|
|
|
status |= IRQ_INPROGRESS; /* we are handling it */
|
|
|
|
}
|
|
|
|
desc->status = status;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If there is no IRQ handler or it was disabled, exit early.
|
|
|
|
* Since we set PENDING, if another processor is handling
|
|
|
|
* a different instance of this same irq, the other processor
|
|
|
|
* will take care of it.
|
|
|
|
*/
|
|
|
|
if (unlikely(!action))
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Edge triggered interrupts need to remember
|
|
|
|
* pending events.
|
|
|
|
* This applies to any hw interrupts that allow a second
|
|
|
|
* instance of the same irq to arrive while we are in do_IRQ
|
|
|
|
* or in the handler. But the code here only handles the _second_
|
|
|
|
* instance of the irq, not the third or fourth. So it is mostly
|
|
|
|
* useful for irq hardware that does not mask cleanly in an
|
|
|
|
* SMP environment.
|
|
|
|
*/
|
|
|
|
for (;;) {
|
|
|
|
irqreturn_t action_ret;
|
|
|
|
|
|
|
|
spin_unlock(&desc->lock);
|
|
|
|
|
IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
of passing regs around manually through all ~1800 interrupt handlers in the
Linux kernel.
The regs pointer is used in few places, but it potentially costs both stack
space and code to pass it around. On the FRV arch, removing the regs parameter
from all the genirq function results in a 20% speed up of the IRQ exit path
(ie: from leaving timer_interrupt() to leaving do_IRQ()).
Where appropriate, an arch may override the generic storage facility and do
something different with the variable. On FRV, for instance, the address is
maintained in GR28 at all times inside the kernel as part of general exception
handling.
Having looked over the code, it appears that the parameter may be handed down
through up to twenty or so layers of functions. Consider a USB character
device attached to a USB hub, attached to a USB controller that posts its
interrupts through a cascaded auxiliary interrupt controller. A character
device driver may want to pass regs to the sysrq handler through the input
layer which adds another few layers of parameter passing.
I've build this code with allyesconfig for x86_64 and i386. I've runtested the
main part of the code on FRV and i386, though I can't test most of the drivers.
I've also done partial conversion for powerpc and MIPS - these at least compile
with minimal configurations.
This will affect all archs. Mostly the changes should be relatively easy.
Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
struct pt_regs *old_regs = set_irq_regs(regs);
And put the old one back at the end:
set_irq_regs(old_regs);
Don't pass regs through to generic_handle_irq() or __do_IRQ().
In timer_interrupt(), this sort of change will be necessary:
- update_process_times(user_mode(regs));
- profile_tick(CPU_PROFILING, regs);
+ update_process_times(user_mode(get_irq_regs()));
+ profile_tick(CPU_PROFILING);
I'd like to move update_process_times()'s use of get_irq_regs() into itself,
except that i386, alone of the archs, uses something other than user_mode().
Some notes on the interrupt handling in the drivers:
(*) input_dev() is now gone entirely. The regs pointer is no longer stored in
the input_dev struct.
(*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
something different depending on whether it's been supplied with a regs
pointer or not.
(*) Various IRQ handler function pointers have been moved to type
irq_handler_t.
Signed-Off-By: David Howells <dhowells@redhat.com>
(cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
2006-10-05 13:55:46 +00:00
|
|
|
action_ret = handle_IRQ_event(irq, action);
|
2005-04-16 22:20:36 +00:00
|
|
|
if (!noirqdebug)
|
IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
of passing regs around manually through all ~1800 interrupt handlers in the
Linux kernel.
The regs pointer is used in few places, but it potentially costs both stack
space and code to pass it around. On the FRV arch, removing the regs parameter
from all the genirq function results in a 20% speed up of the IRQ exit path
(ie: from leaving timer_interrupt() to leaving do_IRQ()).
Where appropriate, an arch may override the generic storage facility and do
something different with the variable. On FRV, for instance, the address is
maintained in GR28 at all times inside the kernel as part of general exception
handling.
Having looked over the code, it appears that the parameter may be handed down
through up to twenty or so layers of functions. Consider a USB character
device attached to a USB hub, attached to a USB controller that posts its
interrupts through a cascaded auxiliary interrupt controller. A character
device driver may want to pass regs to the sysrq handler through the input
layer which adds another few layers of parameter passing.
I've build this code with allyesconfig for x86_64 and i386. I've runtested the
main part of the code on FRV and i386, though I can't test most of the drivers.
I've also done partial conversion for powerpc and MIPS - these at least compile
with minimal configurations.
This will affect all archs. Mostly the changes should be relatively easy.
Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
struct pt_regs *old_regs = set_irq_regs(regs);
And put the old one back at the end:
set_irq_regs(old_regs);
Don't pass regs through to generic_handle_irq() or __do_IRQ().
In timer_interrupt(), this sort of change will be necessary:
- update_process_times(user_mode(regs));
- profile_tick(CPU_PROFILING, regs);
+ update_process_times(user_mode(get_irq_regs()));
+ profile_tick(CPU_PROFILING);
I'd like to move update_process_times()'s use of get_irq_regs() into itself,
except that i386, alone of the archs, uses something other than user_mode().
Some notes on the interrupt handling in the drivers:
(*) input_dev() is now gone entirely. The regs pointer is no longer stored in
the input_dev struct.
(*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
something different depending on whether it's been supplied with a regs
pointer or not.
(*) Various IRQ handler function pointers have been moved to type
irq_handler_t.
Signed-Off-By: David Howells <dhowells@redhat.com>
(cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
2006-10-05 13:55:46 +00:00
|
|
|
note_interrupt(irq, desc, action_ret);
|
2006-11-22 17:32:06 +00:00
|
|
|
|
|
|
|
spin_lock(&desc->lock);
|
2005-04-16 22:20:36 +00:00
|
|
|
if (likely(!(desc->status & IRQ_PENDING)))
|
|
|
|
break;
|
|
|
|
desc->status &= ~IRQ_PENDING;
|
|
|
|
}
|
|
|
|
desc->status &= ~IRQ_INPROGRESS;
|
|
|
|
|
|
|
|
out:
|
|
|
|
/*
|
|
|
|
* The ->end() handler has to deal with interrupts which got
|
|
|
|
* disabled while the handler was running.
|
|
|
|
*/
|
[PATCH] genirq: rename desc->handler to desc->chip
This patch-queue improves the generic IRQ layer to be truly generic, by adding
various abstractions and features to it, without impacting existing
functionality.
While the queue can be best described as "fix and improve everything in the
generic IRQ layer that we could think of", and thus it consists of many
smaller features and lots of cleanups, the one feature that stands out most is
the new 'irq chip' abstraction.
The irq-chip abstraction is about describing and coding and IRQ controller
driver by mapping its raw hardware capabilities [and quirks, if needed] in a
straightforward way, without having to think about "IRQ flow"
(level/edge/etc.) type of details.
This stands in contrast with the current 'irq-type' model of genirq
architectures, which 'mixes' raw hardware capabilities with 'flow' details.
The patchset supports both types of irq controller designs at once, and
converts i386 and x86_64 to the new irq-chip design.
As a bonus side-effect of the irq-chip approach, chained interrupt controllers
(master/slave PIC constructs, etc.) are now supported by design as well.
The end result of this patchset intends to be simpler architecture-level code
and more consolidation between architectures.
We reused many bits of code and many concepts from Russell King's ARM IRQ
layer, the merging of which was one of the motivations for this patchset.
This patch:
rename desc->handler to desc->chip.
Originally i did not want to do this, because it's a big patch. But having
both "desc->handler", "desc->handle_irq" and "action->handler" caused a
large degree of confusion and made the code appear alot less clean than it
truly is.
I have also attempted a dual approach as well by introducing a
desc->chip alias - but that just wasnt robust enough and broke
frequently.
So lets get over with this quickly. The conversion was done automatically
via scripts and converts all the code in the kernel.
This renaming patch is the first one amongst the patches, so that the
remaining patches can stay flexible and can be merged and split up
without having some big monolithic patch act as a merge barrier.
[akpm@osdl.org: build fix]
[akpm@osdl.org: another build fix]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-06-29 09:24:36 +00:00
|
|
|
desc->chip->end(irq);
|
2005-04-16 22:20:36 +00:00
|
|
|
spin_unlock(&desc->lock);
|
|
|
|
|
|
|
|
return 1;
|
|
|
|
}
|
2006-09-26 06:32:07 +00:00
|
|
|
#endif
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-07-03 07:25:06 +00:00
|
|
|
|
2008-08-20 03:50:05 +00:00
|
|
|
#ifdef CONFIG_TRACE_IRQFLAGS
|
2008-10-15 13:27:23 +00:00
|
|
|
/*
|
|
|
|
* lockdep: we want to handle all irq_desc locks as a single lock-class:
|
|
|
|
*/
|
|
|
|
static struct lock_class_key irq_desc_lock_class;
|
|
|
|
|
2006-07-03 07:25:06 +00:00
|
|
|
void early_init_irq_lock_class(void)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
2008-08-20 03:49:47 +00:00
|
|
|
for (i = 0; i < nr_irqs; i++)
|
2006-07-03 07:25:06 +00:00
|
|
|
lockdep_set_class(&irq_desc[i].lock, &irq_desc_lock_class);
|
|
|
|
}
|
|
|
|
#endif
|