The patch titled
clockevents: prevent clockevent event_handler ending up handler_noop
has been removed from the -mm tree. Its filename was
clockevents-prevent-clockevent-event_handler-ending-up-handler_noop.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: clockevents: prevent clockevent event_handler ending up handler_noop
From: Venki Pallipadi <venkatesh.pallipadi@xxxxxxxxx>
There is a ordering related problem with clockevents code, due to which
clockevents_register_device() called after tickless/highres switch will
not work. The new clockevent ends up with clockevents_handle_noop as
event handler, resulting in no timer activity.
The problematic path seems to be
* old device already has hrtimer_interrupt as the event_handler
* new clockevent device registers with a higher rating
* tick_check_new_device() is called
* clockevents_exchange_device() gets called
* old->event_handler is set to clockevents_handle_noop
* tick_setup_device() is called for the new device
* which sets new->event_handler using the old->event_handler which is noop.
Change the ordering so that new device inherits the proper handler.
This does not have any issue in normal case as most likely all the
clockevent devices are setup before the highres switch. But, can
potentially be affecting some corner case where HPET force detect happens
after the highres switch. This was a problem with HPET in MSI mode code
that we have been experimenting with.
Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@xxxxxxxxx>
Signed-off-by: Shaohua Li <shaohua.li@xxxxxxxxx>
Acked-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Cc: Ingo Molnar <mingo@xxxxxxx>
Cc: john stultz <johnstul@xxxxxxxxxx>
Cc: <stable@xxxxxxxxxx> [2.6.25.x, 2.6.26.x]
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/clockchips.h | 2 ++
kernel/time/clockevents.c | 3 +--
kernel/time/tick-common.c | 1 +
3 files changed, 4 insertions(+), 2 deletions(-)
diff -puN include/linux/clockchips.h~clockevents-prevent-clockevent-event_handler-ending-up-handler_noop include/linux/clockchips.h
--- a/include/linux/clockchips.h~clockevents-prevent-clockevent-event_handler-ending-up-handler_noop
+++ a/include/linux/clockchips.h
@@ -127,6 +127,8 @@ extern int clockevents_register_notifier
extern int clockevents_program_event(struct clock_event_device *dev,
ktime_t expires, ktime_t now);
+extern void clockevents_handle_noop(struct clock_event_device *dev);
+
#ifdef CONFIG_GENERIC_CLOCKEVENTS
extern void clockevents_notify(unsigned long reason, void *arg);
#else
diff -puN kernel/time/clockevents.c~clockevents-prevent-clockevent-event_handler-ending-up-handler_noop kernel/time/clockevents.c
--- a/kernel/time/clockevents.c~clockevents-prevent-clockevent-event_handler-ending-up-handler_noop
+++ a/kernel/time/clockevents.c
@@ -177,7 +177,7 @@ void clockevents_register_device(struct
/*
* Noop handler when we shut down an event device
*/
-static void clockevents_handle_noop(struct clock_event_device *dev)
+void clockevents_handle_noop(struct clock_event_device *dev)
{
}
@@ -199,7 +199,6 @@ void clockevents_exchange_device(struct
* released list and do a notify add later.
*/
if (old) {
- old->event_handler = clockevents_handle_noop;
clockevents_set_mode(old, CLOCK_EVT_MODE_UNUSED);
list_del(&old->list);
list_add(&old->list, &clockevents_released);
diff -puN kernel/time/tick-common.c~clockevents-prevent-clockevent-event_handler-ending-up-handler_noop kernel/time/tick-common.c
--- a/kernel/time/tick-common.c~clockevents-prevent-clockevent-event_handler-ending-up-handler_noop
+++ a/kernel/time/tick-common.c
@@ -161,6 +161,7 @@ static void tick_setup_device(struct tic
} else {
handler = td->evtdev->event_handler;
next_event = td->evtdev->next_event;
+ td->evtdev->event_handler = clockevents_handle_noop;
}
td->evtdev = newdev;
_
Patches currently in -mm which might be from venkatesh.pallipadi@xxxxxxxxx are
origin.patch
linux-next.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
