Sergei Shtylyov writes: > I've just realized that I've missed the call to account_process_time() in > the new timer_interrupt(). :-<
Which is bogus. I had removed it in the version of the patch that I posted in early September, but apparently it crept back in. > Anyway, this leads to each tick being accounted twice if the > deterministic > accounting is not enabled -- first by timer_interrupt() and then by the > hrtimers core, doesn't it? Yep. Actually, I thought I was told that with CFS, the total process time was accounted accurately using sched_clock(), then apportioned between utime and stime (using counts of ticks in user/system state, which are somewhat inaccurate). At the time I thought that would be OK, but now I'm not so sure. Paul. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
