> by doing this at kernel level, we can: > - measure exactly the guest time, > - move this part of system time to user time (as you think it should be > user time), > - have consistency between system, user and guest time, > - report values in /proc/state and /proc/<pid>/state, at system wide level > > I'm not sure we can measure the guest time at the qemu user level. > > Perhaps Rusty can say what he thinks about this ? > Even if we cannot _now_, isn't that an easier, and safer change? (and I don't think we lose anything by design). Although I don't know KVM to a that deep level, I think it should be possible to keep the virtual cpus in different process (or threads), and take the accounting time from there. Perfectly possible to know the time we spent running (user time), and the time the hypervisor spent doing things on our behalf (system time). $0.02. -- Glauber de Oliveira Costa. "Free as in Freedom" http://glommer.net "The less confident you are, the more serious you have to act." _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
