On Fri, 2015-06-12 at 10:55 +0200, Fredrik Markstrom wrote: > The scaling mechanism might sometimes cause top to report >100% > (sometimes > 1000%) cpu usage for a single thread. This patch makes > sure that stime+utime corresponds to the actual runtime of the thread.
This Changelog is inadequate, it does not explain the actual problem. > +static DEFINE_SPINLOCK(prev_time_lock); global (spin)locks are bad. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
