* 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
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
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 curr
3 matches
Mail list logo