Dan Hecht wrote:
> So, yes, it is per-vcpu. But, the sched_clock() samples are rebased
> when processes are migrated between runqueues; search sched.c for
> most_recent_timestamp. It's not perfect since most_recent_timestamp
> between cpu0 and cpu1 do not correspond to the exact same instant, but
> does prevent negative sleep time and is fairly close.
Yes, I noticed that when I looked more carefully, but I wasn't sure
whether it would be sufficient to make it all work out.
J
-
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/
