[lkml]   [2010]   [Dec]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[PATCH] [197/223] nohz/s390: fix arch_needs_cpu() return value on offline cpus
    2.6.35-longterm review patch.  If anyone has any objections, please let me know.

    From: Heiko Carstens <>

    commit 398812159e328478ae49b4bd01f0d71efea96c39 upstream.

    This fixes the same problem as described in the patch "nohz: fix
    printk_needs_cpu() return value on offline cpus" for the arch_needs_cpu()

    arch_needs_cpu() may return 1 if called on offline cpus. When a cpu gets
    offlined it schedules the idle process which, before killing its own cpu,
    will call tick_nohz_stop_sched_tick().
    That function in turn will call arch_needs_cpu() in order to check if the
    local tick can be disabled. On offline cpus this function should naturally
    return 0 since regardless if the tick gets disabled or not the cpu will be
    dead short after. That is besides the fact that __cpu_disable() should already
    have made sure that no interrupts on the offlined cpu will be delivered anyway.

    In this case it prevents tick_nohz_stop_sched_tick() to call
    select_nohz_load_balancer(). No idea if that really is a problem. However what
    made me debug this is that on 2.6.32 the function get_nohz_load_balancer() is
    used within __mod_timer() to select a cpu on which a timer gets enqueued.
    If arch_needs_cpu() returns 1 then the nohz_load_balancer cpu doesn't get
    updated when a cpu gets offlined. It may contain the cpu number of an offline
    cpu. In turn timers get enqueued on an offline cpu and not very surprisingly
    they never expire and cause system hangs.

    This has been observed 2.6.32 kernels. On current kernels __mod_timer() uses
    get_nohz_timer_target() which doesn't have that problem. However there might
    be other problems because of the too early exit tick_nohz_stop_sched_tick()
    in case a cpu goes offline.

    This specific bug was indrocuded with 3c5d92a0 "nohz: Introduce

    In this case a cpu hotplug notifier is used to fix the issue in order to keep
    the normal/fast path small. All we need to do is to clear the condition that
    makes arch_needs_cpu() return 1 since it is just a performance improvement
    which is supposed to keep the local tick running for a short period if a cpu
    goes idle. Nothing special needs to be done except for clearing the condition.

    Acked-by: Peter Zijlstra <>
    Signed-off-by: Heiko Carstens <>
    Signed-off-by: Martin Schwidefsky <>
    Signed-off-by: Greg Kroah-Hartman <>
    Signed-off-by: Andi Kleen <>

    arch/s390/kernel/vtime.c | 19 +++++++++++++++++++
    1 file changed, 19 insertions(+)

    Index: linux/arch/s390/kernel/vtime.c
    --- linux.orig/arch/s390/kernel/vtime.c
    +++ linux/arch/s390/kernel/vtime.c
    @@ -19,6 +19,7 @@
    #include <linux/kernel_stat.h>
    #include <linux/rcupdate.h>
    #include <linux/posix-timers.h>
    +#include <linux/cpu.h>

    #include <asm/s390_ext.h>
    #include <asm/timer.h>
    @@ -565,6 +566,23 @@ void init_cpu_vtimer(void)

    +static int __cpuinit s390_nohz_notify(struct notifier_block *self,
    + unsigned long action, void *hcpu)
    + struct s390_idle_data *idle;
    + long cpu = (long) hcpu;
    + idle = &per_cpu(s390_idle, cpu);
    + switch (action) {
    + case CPU_DYING:
    + case CPU_DYING_FROZEN:
    + idle->nohz_delay = 0;
    + default:
    + break;
    + }
    + return NOTIFY_OK;
    void __init vtime_init(void)
    /* request the cpu timer external interrupt */
    @@ -573,5 +591,6 @@ void __init vtime_init(void)

    /* Enable cpu timer interrupts on the boot cpu. */
    + cpu_notifier(s390_nohz_notify, 0);

     \ /
      Last update: 2010-12-13 00:55    [from the cache]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site