From: Rusty Russell Subject: Re: [PATCH 0/4] Virtual Machine Time Accounting Date: Tue, 21 Aug 2007 09:30:56 +1000 Message-ID: <1187652656.19435.143.camel@localhost.localdomain> References: <46C99371.7070705@bull.net> <18121.39541.790665.686081@stoffel.org> <46C9A7AB.1030003@bull.net> <46C9BD8F.4070807@goop.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Laurent Vivier , kvm-devel , Ingo Molnar , John Stoffel , linux-kernel , virtualization To: Jeremy Fitzhardinge Return-path: In-Reply-To: <46C9BD8F.4070807@goop.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Mon, 2007-08-20 at 09:13 -0700, 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//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)? No, unfortunately it's accumulated as system time. Rusty.