On Mon, Jan 28, 2013 at 8:04 PM, Frederic Weisbecker <[email protected]> wrote: > While remotely reading the cputime of a task running in a > full dynticks CPU, the values stored in utime/stime fields > of struct task_struct may be stale. Its values may be those > of the last kernel <-> user transition time snapshot and > we need to add the tickless time spent since this snapshot. > > To fix this, flush the cputime of the dynticks CPUs on > kernel <-> user transition and record the time / context > where we did this. Then on top of this snapshot and the current > time, perform the fixup on the reader side from task_times() > accessors. > > Signed-off-by: Frederic Weisbecker <[email protected]> > Cc: Andrew Morton <[email protected]> > Cc: Ingo Molnar <[email protected]> > Cc: Li Zhong <[email protected]> > Cc: Namhyung Kim <[email protected]> > Cc: Paul E. McKenney <[email protected]> > Cc: Paul Gortmaker <[email protected]> > Cc: Peter Zijlstra <[email protected]> > Cc: Steven Rostedt <[email protected]> > Cc: Thomas Gleixner <[email protected]> > [fixed kvm module related build errors] > Signed-off-by: Sedat Dilek <[email protected]> >
Can you explain a bit what is the difference between "3.8-rc4-nohz3" and "full-dynticks-cputime-for-mingo" patchsets? Does the latter need no more EXPORT_SYMBOL_GPL for vtime_guest_enter() and vtime_guest_exit() when CONFIG_KVM=m (see [1])? - Sedat - [1] https://lkml.org/lkml/2013/1/23/473 -- 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/
