diff options
Diffstat (limited to 'patches/linux-2.6.17/fix-hz-suspend.patch')
| -rw-r--r-- | patches/linux-2.6.17/fix-hz-suspend.patch | 26 |
1 files changed, 0 insertions, 26 deletions
diff --git a/patches/linux-2.6.17/fix-hz-suspend.patch b/patches/linux-2.6.17/fix-hz-suspend.patch deleted file mode 100644 index d06a658cd8..0000000000 --- a/patches/linux-2.6.17/fix-hz-suspend.patch +++ /dev/null @@ -1,26 +0,0 @@ -diff -pruN ../orig-linux-2.6.17/kernel/timer.c ./kernel/timer.c ---- ../orig-linux-2.6.17/kernel/timer.c 2006-06-18 02:49:35.000000000 +0100 -+++ ./kernel/timer.c 2007-01-08 15:14:52.000000000 +0000 -@@ -557,6 +557,22 @@ found: - if (time_before(expires, jiffies)) - return jiffies; - -+ /* -+ * It can happen that other CPUs service timer IRQs and increment -+ * jiffies, but we have not yet got a local timer tick to process -+ * the timer wheels. In that case, the expiry time can be before -+ * jiffies, but since the high-resolution timer here is relative to -+ * jiffies, the default expression when high-resolution timers are -+ * not active, -+ * -+ * time_before(MAX_JIFFY_OFFSET + jiffies, expires) -+ * -+ * would falsely evaluate to true. If that is the case, just -+ * return jiffies so that we can immediately fire the local timer -+ */ -+ if (time_before(expires, jiffies)) -+ return jiffies; -+ - if (time_before(hr_expires, expires)) - return hr_expires; - |