Re: [PATCH v1] timer: Forward timer base before migrating timers

2018-01-18 Thread Thomas Gleixner
On Wed, 17 Jan 2018, Lingutla Chandrasekhar wrote: > In case when timers are migrated to a CPU, after it exits > idle, but before timer base is forwarded, either from > run_timer_softirq()/mod_timer()/add_timer_on(), it's > possible that migrated timers are queued, based on older > clock value.

Re: [PATCH v1] timer: Forward timer base before migrating timers

2018-01-18 Thread Thomas Gleixner
On Wed, 17 Jan 2018, Lingutla Chandrasekhar wrote: > In case when timers are migrated to a CPU, after it exits > idle, but before timer base is forwarded, either from > run_timer_softirq()/mod_timer()/add_timer_on(), it's > possible that migrated timers are queued, based on older > clock value.

[PATCH v1] timer: Forward timer base before migrating timers

2018-01-17 Thread Lingutla Chandrasekhar
In case when timers are migrated to a CPU, after it exits idle, but before timer base is forwarded, either from run_timer_softirq()/mod_timer()/add_timer_on(), it's possible that migrated timers are queued, based on older clock value. This can cause delays in handling those timers. For example,

[PATCH v1] timer: Forward timer base before migrating timers

2018-01-17 Thread Lingutla Chandrasekhar
In case when timers are migrated to a CPU, after it exits idle, but before timer base is forwarded, either from run_timer_softirq()/mod_timer()/add_timer_on(), it's possible that migrated timers are queued, based on older clock value. This can cause delays in handling those timers. For example,