All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: edward.donovan@numble.net
Cc: linux-kernel@vger.kernel.org, maciej.rutecki@gmail.com
Subject: Re: [PATCH] genirq: spurious.c: fix regression that broke irqfixup,irqpoll
Date: Wed, 2 Nov 2011 19:02:35 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.02.1111021901440.2829@ionos> (raw)
In-Reply-To: <1320175784-6745-1-git-send-email-edward.donovan@numble.net>

On Tue, 1 Nov 2011, edward.donovan@numble.net wrote:

> From: Edward Donovan <edward.donovan@numble.net>
> 
> commit  d05c65fff0 ("genirq: spurious: Run only one poller at a time")
> introduced a regression, leaving the boot options 'irqfixup' and
> 'irqpoll' non-functional.  The patch placed tests in each function, to
> exit if the function is already running.  The test in 'misrouted_irq'
> exited when it should have proceeded, effectively disabling
> 'misrouted_irq' and 'poll_spurious_irqs'.  Reversing the "==" operator
> to "!=" fixes the regression.
> 
> Signed-off-by: Edward Donovan <edward.donovan@numble.net>

Good catch! I was staring at it with my conference and flu damaged
brain ....

Thanks,

	tglx

> ---
>  kernel/irq/spurious.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/kernel/irq/spurious.c b/kernel/irq/spurious.c
> index aa57d5d..b5f4742 100644
> --- a/kernel/irq/spurious.c
> +++ b/kernel/irq/spurious.c
> @@ -115,7 +115,7 @@ static int misrouted_irq(int irq)
>  	struct irq_desc *desc;
>  	int i, ok = 0;
>  
> -	if (atomic_inc_return(&irq_poll_active) == 1)
> +	if (atomic_inc_return(&irq_poll_active) != 1)
>  		goto out;
>  
>  	irq_poll_cpu = smp_processor_id();
> -- 
> 1.7.5.4
> 
> 

  reply	other threads:[~2011-11-02 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 19:29 [PATCH] genirq: spurious.c: fix regression that broke irqfixup,irqpoll edward.donovan
2011-11-02 18:02 ` Thomas Gleixner [this message]
2011-11-03 20:25   ` Edward Donovan

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.02.1111021901440.2829@ionos \
    --to=tglx@linutronix.de \
    --cc=edward.donovan@numble.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.rutecki@gmail.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 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.