mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, tony.luck@intel.com, jes@sgi.com,
	manfred@colorfullife.com, akpm@linux-foundation.org
Subject: Re: [PATCH] prevent ia64 from invoking irq handlers on offline CPUs
Date: Sun, 31 Aug 2008 19:46:33 +0200	[thread overview]
Message-ID: <19f34abd0808311046g47907414wf3ef939d0a7bbfdb@mail.gmail.com> (raw)
In-Reply-To: <20080831172814.GA15087@linux.vnet.ibm.com>

On Sun, Aug 31, 2008 at 7:28 PM, Paul E. McKenney
<paulmck@linux.vnet.ibm.com> wrote:
> Make ia64 refrain from clearing a given to-be-offlined CPU's bit in the
> cpu_online_mask until it has processed pending irqs.  This change
> prevents other CPUs from being blindsided by an apparently offline CPU
> nevertheless changing globally visible state.
>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> ---
>
>  smpboot.c |    3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/ia64/kernel/smpboot.c b/arch/ia64/kernel/smpboot.c
> index bcea81e..7a90f42 100644
> --- a/arch/ia64/kernel/smpboot.c
> +++ b/arch/ia64/kernel/smpboot.c
> @@ -741,8 +741,6 @@ int __cpu_disable(void)
>                        return -EBUSY;
>        }
>
> -       cpu_clear(cpu, cpu_online_map);
> -
>        if (migrate_platform_irqs(cpu)) {
>                cpu_set(cpu, cpu_online_map);
>                return (-EBUSY);
> @@ -751,6 +749,7 @@ int __cpu_disable(void)
>        remove_siblinginfo(cpu);
>        cpu_clear(cpu, cpu_online_map);
>        fixup_irqs();
> +       cpu_clear(cpu, cpu_online_map);
>        local_flush_tlb_all();
>        cpu_clear(cpu, cpu_callin_map);
>        return 0;

Hm. Maybe my eyes are going bad. But isn't that now clearing the cpu
both before and after calling fixup_irqs()?


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

  reply	other threads:[~2008-08-31 17:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-31 17:28 Paul E. McKenney
2008-08-31 17:46 ` Vegard Nossum [this message]
2008-08-31 17:51   ` Paul E. McKenney
2008-08-31 17:53     ` Vegard Nossum
2008-08-31 18:06       ` Paul E. McKenney
2008-08-31 19:08         ` Vegard Nossum
2008-08-31 20:08           ` Paul E. McKenney

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=19f34abd0808311046g47907414wf3ef939d0a7bbfdb@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=tony.luck@intel.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 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®