1. 13 May, 2009 2 commits
    • Arun R Bharadwaj's avatar
      timers: Identifying the existing pinned timers · 5c333864
      Arun R Bharadwaj authored
      * Arun R Bharadwaj <arun@linux.vnet.ibm.com> [2009-04-16 12:11:36]:
      
      The following pinned hrtimers have been identified and marked:
      1)sched_rt_period_timer
      2)tick_sched_timer
      3)stack_trace_timer_fn
      
      [ tglx: fixup the hrtimer pinned mode ]
      Signed-off-by: default avatarArun R Bharadwaj <arun@linux.vnet.ibm.com>
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      5c333864
    • Arun R Bharadwaj's avatar
      timers: Framework for identifying pinned timers · 597d0275
      Arun R Bharadwaj authored
      * Arun R Bharadwaj <arun@linux.vnet.ibm.com> [2009-04-16 12:11:36]:
      
      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.
      
      For regular timers, the currently existing add_timer_on() can be used
      queue pinned timers and subsequently mod_timer_pinned() can be used
      to modify the 'expires' field.
      
      For hrtimers, new modes HRTIMER_ABS_PINNED and HRTIMER_REL_PINNED are
      added to queue cpu-pinned hrtimer.
      
      [ tglx: use .._PINNED mode argument instead of creating tons of new
      functions ]
      Signed-off-by: default avatarArun R Bharadwaj <arun@linux.vnet.ibm.com>
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      597d0275
  2. 02 May, 2009 1 commit
  3. 29 Apr, 2009 14 commits
  4. 28 Apr, 2009 23 commits