Am 20.05.2013 18:01, schrieb Frederic Weisbecker: > While computing the cputime delta of dynticks CPUs, > we are mixing up clocks of differents natures:
[...] > As a consequence, some strange behaviour with unstable tsc > has been observed such as non progressing constant zero cputime. > (The 'top' command showing no load). This happens for example on my trusty ThinkPad X200s (family 6 model 23 stepping 10 Core 2 duo), seriously confusing its user (me :-). > Fix this by only using local_clock(), or its irq safe/remote > equivalent, in vtime code. > > Reported-by: Mike Galbraith <[email protected]> > Suggested-by: Mike Galbraith <[email protected]> > Cc: Steven Rostedt <[email protected]> > Cc: Paul E. McKenney <[email protected]> > Cc: Ingo Molnar <[email protected]> > Cc: Thomas Gleixner <[email protected]> > Cc: Peter Zijlstra <[email protected]> > Cc: Borislav Petkov <[email protected]> > Cc: Li Zhong <[email protected]> > Cc: Mike Galbraith <[email protected]> > Signed-off-by: Frederic Weisbecker <[email protected]> FWIW: Tested-by: Stefan Seyfried <[email protected]> This patch fixes the 0% CPU issue on openSUSE Factory kernels for me. Best regards, Stefan -- Stefan Seyfried Linux Consultant & Developer -- GPG Key: 0x731B665B B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
