Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 048a0e8f authored by Paul E. McKenney's avatar Paul E. McKenney Committed by Paul E. McKenney
Browse files

timer: Fix mod_timer_pinned() header comment 



The mod_timer_pinned() header comment states that it prevents timers
from being migrated to a different CPU.  This is not the case, instead,
it ensures that the timer is posted to the current CPU, but does nothing
to prevent CPU-hotplug operations from migrating the timer.

This commit therefore brings the comment header into alignment with
reality.

Signed-off-by: default avatarPaul E. McKenney <paul.mckenney@linaro.org>
Signed-off-by: default avatarPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Acked-by: default avatarSteven Rostedt <rostedt@goodmis.org>
parent 6d813391

kernel/timer.c

+7 −1
Original line number Original line Diff line number Diff line
@@ -861,7 +861,13 @@ EXPORT_SYMBOL(mod_timer); 
 *

 *

 * mod_timer_pinned() is a way to update the expire field of an

 * mod_timer_pinned() is a way to update the expire field of an

 * active timer (if the timer is inactive it will be activated)

 * active timer (if the timer is inactive it will be activated)

 * and not allow the timer to be migrated to a different CPU.

 * and to ensure that the timer is scheduled on the current CPU.

 *

 * Note that this does not prevent the timer from being migrated

 * when the current CPU goes offline.  If this is a problem for

 * you, use CPU-hotplug notifiers to handle it correctly, for

 * example, cancelling the timer when the corresponding CPU goes

 * offline.

 *

 *

 * mod_timer_pinned(timer, expires) is equivalent to:

 * mod_timer_pinned(timer, expires) is equivalent to:

 *

 *