Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=28f36f8fbf5f3718f7095055c1911a67d200dda1
Commit:     28f36f8fbf5f3718f7095055c1911a67d200dda1
Parent:     43999d9e4e3133bfe0a55589037796386b012a68
Author:     Guillaume Chazarain <[EMAIL PROTECTED]>
AuthorDate: Fri Mar 16 21:07:36 2007 +0100
Committer:  Andi Kleen <[EMAIL PROTECTED]>
CommitDate: Fri Mar 16 21:07:36 2007 +0100

    [PATCH] i386: Don't use the TSC in sched_clock if unstable
    
    
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f9690982b8c2f9a2c65acdc113e758ec356676a3
    caused a regression by letting sched_clock use the TSC even when cpufreq
    disabled it. This caused scheduling weirdnesses.
    
    Signed-off-by: Guillaume Chazarain <[EMAIL PROTECTED]>
    Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
 arch/i386/kernel/tsc.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/i386/kernel/tsc.c b/arch/i386/kernel/tsc.c
index 602660d..0e65f7a 100644
--- a/arch/i386/kernel/tsc.c
+++ b/arch/i386/kernel/tsc.c
@@ -105,7 +105,7 @@ unsigned long long sched_clock(void)
        /*
         * Fall back to jiffies if there's no TSC available:
         */
-       if (unlikely(tsc_disable))
+       if (tsc_unstable || unlikely(tsc_disable))
                /* No locking but a rare wrong value is not a big deal: */
                return (jiffies_64 - INITIAL_JIFFIES) * (1000000000 / HZ);
 
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to