From: Thomas Gleixner <tglx@linutronix.de>
To: Rabin Vincent <rabin@rab.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: handle shared irqs in handle_nested_irq()
Date: Thu, 28 Oct 2010 20:54:18 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1010282053180.2692@localhost6.localdomain6> (raw)
In-Reply-To: <1288288718-1188-1-git-send-email-rabin@rab.in>
On Thu, 28 Oct 2010, Rabin Vincent wrote:
> Allow shared irqs to work when nested threads are used for handling
> threaded interrupts.
Why do we want this ? handle_nested_irq() is called from a interrupt
demultiplexer, so why would we need shared interrupts for this ?
Thanks,
tglx
> Signed-off-by: Rabin Vincent <rabin@rab.in>
> ---
> kernel/irq/chip.c | 7 +++++--
> 1 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
> index baa5c4a..94a45a9 100644
> --- a/kernel/irq/chip.c
> +++ b/kernel/irq/chip.c
> @@ -418,8 +418,8 @@ static inline void unmask_irq(struct irq_desc *desc)
> void handle_nested_irq(unsigned int irq)
> {
> struct irq_desc *desc = irq_to_desc(irq);
> + irqreturn_t action_ret = IRQ_NONE;
> struct irqaction *action;
> - irqreturn_t action_ret;
>
> might_sleep();
>
> @@ -434,7 +434,10 @@ void handle_nested_irq(unsigned int irq)
> desc->status |= IRQ_INPROGRESS;
> raw_spin_unlock_irq(&desc->lock);
>
> - action_ret = action->thread_fn(action->irq, action->dev_id);
> + do {
> + action_ret |= action->thread_fn(action->irq, action->dev_id);
> + action = action->next;
> + } while (action);
> if (!noirqdebug)
> note_interrupt(irq, desc, action_ret);
>
> --
> 1.7.2.3
>
next prev parent reply other threads:[~2010-10-28 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 17:58 Rabin Vincent
2010-10-28 18:54 ` Thomas Gleixner [this message]
2010-10-29 15:21 ` Rabin Vincent
2010-10-29 15:26 ` Thomas Gleixner
2010-10-29 15:57 ` Rabin Vincent
2010-10-29 16:34 ` Thomas Gleixner
2010-10-29 16:49 ` Rabin Vincent
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=alpine.LFD.2.00.1010282053180.2692@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin@rab.in \
/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
all inboxes | Powered by JetHome®