diff options
| author | kfraser@localhost.localdomain <kfraser@localhost.localdomain> | 2007-03-09 18:30:52 +0000 |
|---|---|---|
| committer | kfraser@localhost.localdomain <kfraser@localhost.localdomain> | 2007-03-09 18:30:52 +0000 |
| commit | bde87bfe0eccc198a6fa6bc54ccbe37718a93182 (patch) | |
| tree | b3394c55b9d0b0c5c6a595aed2024b724145ae1c /patches | |
| parent | eb1a565927c0fdcd89be41f6d063c458539cca8d (diff) | |
| download | xen-bde87bfe0eccc198a6fa6bc54ccbe37718a93182.tar.gz xen-bde87bfe0eccc198a6fa6bc54ccbe37718a93182.tar.bz2 xen-bde87bfe0eccc198a6fa6bc54ccbe37718a93182.zip | |
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@novell.com>
Diffstat (limited to 'patches')
| -rw-r--r-- | patches/linux-2.6.18/softlockup-no-idle-hz.patch | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/patches/linux-2.6.18/softlockup-no-idle-hz.patch b/patches/linux-2.6.18/softlockup-no-idle-hz.patch index 6799bfc4bf..d98edac8f2 100644 --- a/patches/linux-2.6.18/softlockup-no-idle-hz.patch +++ b/patches/linux-2.6.18/softlockup-no-idle-hz.patch @@ -34,7 +34,7 @@ diff -pruN ../orig-linux-2.6.18/kernel/softlockup.c ./kernel/softlockup.c + !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); +} + /* |