Jeremy Fitzhardinge wrote: > Laurent Vivier wrote: > >> functionnalities: >> >> - allow to measure time spent by a CPU in a virtual CPU. >> - allow to display in /proc/state this value by CPU >> - allow to display in /proc/<pid>/state this value by process >> - allow KVM to use these 3 previous functionnalities >> >> > > So, currently time spent in a kvm guest is accumulated as qemu-kvm > usertime, right? Given that qemu knows when its running in qemu vs > guest context, couldn't it provide the breakdown between user and guest > time (ditto lguest)? >
qemu doesn't (and shouldn't) do accounting; that's best done by interrupt driven code. The patches do account for guest time in a separate counter; guest time is added to both user time and the new counter. This allows an old 'top' to see guest time (accounted as user time), and a new 'top' to separate guest time and user time by performing the appropriate mathematical operation. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
