[lkml]   [2018]   [Jan]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v4 02/36] hrtimer: Correct blantanly wrong comment
On Thu, Dec 21, 2017 at 11:41:31AM +0100, Anna-Maria Gleixner wrote:
> From: Thomas Gleixner <>
> The protection of a hrtimer which runs its callback against migration to a
> different CPU has nothing to do with hard interrupt context.
> The protection against migration of a hrtimer running the expiry callback
> is the pointer in the cpu_base which holds a pointer to the currently
> running timer. This pointer is evaluated in the code which potentially
> switches the timer base and makes sure it's kept on the CPU on which the
> callback is running.
> Reported-by: Anna-Maria Gleixner <>
> Signed-off-by: Thomas Gleixner <>
> Signed-off-by: Anna-Maria Gleixner <>

Reviewed-by: Frederic Weisbecker <>

 \ /
  Last update: 2018-01-14 23:24    [W:0.152 / U:1.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site