Re: [PATCH v4 02/36] hrtimer: Correct blantanly wrong comment

[Frederic Weisbecker]

On Thu, Dec 21, 2017 at 11:41:31AM +0100, Anna-Maria Gleixner wrote:
> From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
> 
> 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 <anna-maria@xxxxxxxxxxxxx>
> Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
> Signed-off-by: Anna-Maria Gleixner <anna-maria@xxxxxxxxxxxxx>

Reviewed-by: Frederic Weisbecker <frederic@xxxxxxxxxx>