Re: [RFC 2/4] timer: don't migrate pinned timers

2014-04-04 Thread Kevin Hilman
Viresh Kumar writes: > On 31 March 2014 21:26, Kevin Hilman wrote: >> Viresh Kumar writes: >>> + if (is_pinned) { >>> + pr_warn("%s: can't migrate pinned timer: %p, removing >>> it\n", >>> + __func__, timer); >> >> printk mess

Re: [RFC 2/4] timer: don't migrate pinned timers

2014-03-31 Thread Viresh Kumar
On 31 March 2014 21:26, Kevin Hilman wrote: > Viresh Kumar writes: >> + if (is_pinned) { >> + pr_warn("%s: can't migrate pinned timer: %p, removing >> it\n", >> + __func__, timer); > > printk message will be confusing: removing

Re: [RFC 2/4] timer: don't migrate pinned timers

2014-03-31 Thread Kevin Hilman
Viresh Kumar writes: > migrate_timer() is called when a CPU goes down and its timers are required to > be > migrated to some other CPU. Its the responsibility of the users of the timer > to > remove it before control reaches to migrate_timers(). > > As these were the pinned timers, the best we

[RFC 2/4] timer: don't migrate pinned timers

2014-03-20 Thread Viresh Kumar
migrate_timer() is called when a CPU goes down and its timers are required to be migrated to some other CPU. Its the responsibility of the users of the timer to remove it before control reaches to migrate_timers(). As these were the pinned timers, the best we can do is: don't migrate these and rep