On Tue, 2011-02-01 at 13:59 -0200, Glauber Costa wrote: > > Because that part is kvm-specific, and this is scheduler general. > It seemed cleaner to me to do it this way. But I can do it differently, > certainly. Well, any steal time clock will be hypervisor specific, but if we agree that anything that enables CONFIG_PARAVIRT_TIME_ACCOUNTING provides a u64 steal_time_clock(int cpu) function then all should be well, right? The bit you have in kvm is almost that, except it assumes cpu == this_cpu. You simply cannot rely on the silly tick accounting to drive any clock, its archaic. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
