[Xen-changelog] [xen-unstable] linux: fix condition for entering tickless state

[Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User kfraser@xxxxxxxxxxxxxxxxxxxxx
# Date 1173465052 0
# Node ID 818da23b7571b3f6f6f12bb80658f9a13ed8b8f3
# Parent  215b799fa181a807aed289e39b56c8e0c463f322
linux: fix condition for entering tickless state

I noticed that timer interrupts were running at full rate regardless
of whether the system was idle.
softlockup_get_next_event() must return the maximum of zero and the
delta to the next event, not the minimum (which is always zero or
negative, yielding zero or a very large positive number as return
value).

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
---
 patches/linux-2.6.18/softlockup-no-idle-hz.patch |    1 -
 1 files changed, 1 deletion(-)

diff -r 215b799fa181 -r 818da23b7571 
patches/linux-2.6.18/softlockup-no-idle-hz.patch
--- a/patches/linux-2.6.18/softlockup-no-idle-hz.patch  Fri Mar 09 18:26:47 
2007 +0000
+++ b/patches/linux-2.6.18/softlockup-no-idle-hz.patch  Fri Mar 09 18:30:52 
2007 +0000
@@ -34,7 +34,7 @@ diff -pruN ../orig-linux-2.6.18/kernel/s
 +                      !per_cpu(watchdog_task, this_cpu))
 +              return MAX_JIFFY_OFFSET;
 +
-+      return min_t(long, 0, touch_timestamp + HZ - jiffies);
++      return max_t(long, 0, touch_timestamp + HZ - jiffies);
 +}
 +
  /*

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog