linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Anton Blanchard <anton@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] powerpc: check_and_cede_processor never cedes
Date: Thu, 28 Jun 2012 17:10:44 +1000	[thread overview]
Message-ID: <1340867444.20977.66.camel@pasglop> (raw)
In-Reply-To: <20120628091352.48d3859d@kryten>

On Thu, 2012-06-28 at 09:13 +1000, Anton Blanchard wrote:
> Hi,
> 
> > I'd rather add a helper, something like lazy_irq_pending()
> > and hide the actual check for the bits in irq_happened, in
> > case we change the scheme again.
> 
> Good idea. Look ok?
> 
> --
> 
> Commit f948501b36c6 ("Make hard_irq_disable() actually hard-disable
> interrupts") caused check_and_cede_processor to stop working.
> ->irq_happened will never be zero right after a hard_irq_disable
> so the compiler removes the call to cede_processor completely.
> 
> The bug was introduced back in the lazy interrupt handling rework
> of 3.4 but was hidden until recently because hard_irq_disable did
> nothing.
> 
> This issue will eventually appear in 3.4 stable since the
> hard_irq_disable fix is marked stable, so mark this one for stable
> too.

Yup, looks good, I'll send to Linus tomorrow.

Cheers,
Ben.

> Signed-off-by: Anton Blanchard <anton@samba.org>  
> Cc: stable@vger.kernel.org
> ---
> 
> v2: create a helper, suggested by Ben.
> 
> Index: linux-build/arch/powerpc/platforms/pseries/processor_idle.c
> ===================================================================
> --- linux-build.orig/arch/powerpc/platforms/pseries/processor_idle.c	2012-06-28 08:55:09.422198154 +1000
> +++ linux-build/arch/powerpc/platforms/pseries/processor_idle.c	2012-06-28 08:57:36.112591023 +1000
> @@ -106,7 +106,7 @@ static void check_and_cede_processor(voi
>  	 * we first hard disable then check.
>  	 */
>  	hard_irq_disable();
> -	if (get_paca()->irq_happened == 0)
> +	if (!lazy_irq_pending())
>  		cede_processor();
>  }
>  
> Index: linux-build/arch/powerpc/include/asm/hw_irq.h
> ===================================================================
> --- linux-build.orig/arch/powerpc/include/asm/hw_irq.h	2012-06-21 09:16:26.265354429 +1000
> +++ linux-build/arch/powerpc/include/asm/hw_irq.h	2012-06-28 08:59:22.082320381 +1000
> @@ -103,6 +103,11 @@ static inline void hard_irq_disable(void
>  /* include/linux/interrupt.h needs hard_irq_disable to be a macro */
>  #define hard_irq_disable	hard_irq_disable
>  
> +static inline bool lazy_irq_pending(void)
> +{
> +	return !!(get_paca()->irq_happened & ~PACA_IRQ_HARD_DIS);
> +}
> +
>  /*
>   * This is called by asynchronous interrupts to conditionally
>   * re-enable hard interrupts when soft-disabled after having

      reply	other threads:[~2012-06-28  7:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 22:45 [PATCH] powerpc: check_and_cede_processor never cedes Anton Blanchard
2012-06-27 22:51 ` Benjamin Herrenschmidt
2012-06-27 23:13   ` Anton Blanchard
2012-06-28  7:10     ` Benjamin Herrenschmidt [this message]

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=1340867444.20977.66.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=anton@samba.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    /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;
as well as URLs for NNTP newsgroup(s).