Messages in this thread | | | Date | Wed, 1 Apr 2009 13:41:46 +0200 | From | Andi Kleen <> | Subject | Re: [v4 RFC PATCH 1/4] timers: Framework for identifying pinned timers |
| |
On Wed, Apr 01, 2009 at 05:02:58PM +0530, Arun R Bharadwaj wrote: > * Arun R Bharadwaj <arun@linux.vnet.ibm.com> [2009-04-01 17:01:28]: > > This patch creates a new framework for identifying cpu-pinned timers > and hrtimers. > > > This framework is needed because pinned timers are expected to fire on > the same CPU on which they are queued. So it is essential to identify > these and not migrate them, in case there are any.
How would that interact with add_timer_on()? You currently only support the current CPU, don't you?
e.g. the new tip x86 machine check polling code relies on add_timer_on staying on that CPU.
-Andi
-- ak@linux.intel.com -- Speaking for myself only.
| |