[lkml]   [2012]   [Apr]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[tip:timers/urgent] tick: Fix oneshot broadcast setup really
    Commit-ID:  b435092f70ec5ebbfb6d075d5bf3c631b49a51de
    Author: Thomas Gleixner <>
    AuthorDate: Wed, 18 Apr 2012 12:08:23 +0200
    Committer: Thomas Gleixner <>
    CommitDate: Wed, 18 Apr 2012 14:00:56 +0200

    tick: Fix oneshot broadcast setup really

    Sven Joachim reported, that suspend/resume on rc3 trips over a NULL
    pointer dereference. Linus spotted the clockevent handler being NULL.

    commit fa4da365b(clockevents: tTack broadcast device mode change in
    tick_broadcast_switch_to_oneshot()) tried to fix a problem with the
    broadcast device setup, which was introduced in commit 77b0d60c5(
    clockevents: Leave the broadcast device in shutdown mode when not

    The initial commit avoided to set up the broadcast device when no
    broadcast request bits were set, but that left the broadcast device
    disfunctional. In consequence deep idle states which need the
    broadcast device were not woken up.

    commit fa4da365b tried to fix that by initializing the state of the
    broadcast facility, but that missed the fact, that nothing initializes
    the event handler and some other state of the underlying clock event

    The fix is to revert both commits and make only the mode setting of
    the clock event device conditional on the state of active broadcast

    That initializes everything except the low level device mode, but this
    happens when the broadcast functionality is invoked by deep idle.

    Reported-and-tested-by: Sven Joachim <>
    Signed-off-by: Thomas Gleixner <>
    Cc: Rafael J. Wysocki <>
    Cc: Linus Torvalds <>
    Cc: Suresh Siddha <>

    kernel/time/tick-broadcast.c | 7 +------
    1 files changed, 1 insertions(+), 6 deletions(-)

    diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
    index bf57abd..119aca5 100644
    --- a/kernel/time/tick-broadcast.c
    +++ b/kernel/time/tick-broadcast.c
    @@ -531,7 +531,6 @@ void tick_broadcast_setup_oneshot(struct clock_event_device *bc)
    int was_periodic = bc->mode == CLOCK_EVT_MODE_PERIODIC;

    bc->event_handler = tick_handle_oneshot_broadcast;
    - clockevents_set_mode(bc, CLOCK_EVT_MODE_ONESHOT);

    /* Take the do_timer update */
    tick_do_timer_cpu = cpu;
    @@ -549,6 +548,7 @@ void tick_broadcast_setup_oneshot(struct clock_event_device *bc)

    if (was_periodic && !cpumask_empty(to_cpumask(tmpmask))) {
    + clockevents_set_mode(bc, CLOCK_EVT_MODE_ONESHOT);
    tick_broadcast_set_event(tick_next_period, 1);
    @@ -577,15 +577,10 @@ void tick_broadcast_switch_to_oneshot(void)
    raw_spin_lock_irqsave(&tick_broadcast_lock, flags);

    tick_broadcast_device.mode = TICKDEV_MODE_ONESHOT;
    - if (cpumask_empty(tick_get_broadcast_mask()))
    - goto end;
    bc = tick_broadcast_device.evtdev;
    if (bc)

    raw_spin_unlock_irqrestore(&tick_broadcast_lock, flags);

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at
     \ /
      Last update: 2012-04-18 22:37    [W:0.030 / U:9.888 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site