forked from rubenslte/android_kernel_samsung_msm8226
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. CRs-fixed: 657837 Change-Id: I244c4c385cd1c47df216feda7b580b2876fab723 Signed-off-by: Paul E. McKenney <paul.mckenney@linaro.org> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Acked-by: Steven Rostedt <rostedt@goodmis.org> Git-commit: 048a0e8f5e1d94c01a5fc70f5b2f2fd2f4527326 Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Signed-off-by: Ramesh Gupta Guntha <rggupt@codeaurora.org>
This commit is contained in:
committed by
Ramesh Gupta Guntha
parent
d3a00bb200
commit
f7f43a5573
+7
-1
@@ -862,7 +862,13 @@ EXPORT_SYMBOL(mod_timer);
|
||||
*
|
||||
* mod_timer_pinned() is a way to update the expire field of an
|
||||
* 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:
|
||||
*
|
||||
|
||||
Reference in New Issue
Block a user