From: Avi Kivity <avi@qumranet.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Laurent Vivier <Laurent.Vivier@bull.net>,
kvm-devel <kvm-devel@lists.sourceforge.net>,
John Stoffel <john@stoffel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [kvm-devel] [PATCH 0/4] Virtual Machine Time Accounting
Date: Tue, 21 Aug 2007 15:54:46 +0300 [thread overview]
Message-ID: <46CAE096.4060606@qumranet.com> (raw)
In-Reply-To: <46C9BD8F.4070807@goop.org>
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
next prev parent reply other threads:[~2007-08-21 12:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 13:13 [PATCH 0/4] Virtual Machine Time Accounting Laurent Vivier
2007-08-20 13:41 ` [kvm-devel] " Avi Kivity
2007-08-20 13:43 ` John Stoffel
2007-08-20 14:39 ` Laurent Vivier
2007-08-20 16:13 ` Jeremy Fitzhardinge
2007-08-20 23:30 ` Rusty Russell
2007-08-21 12:54 ` Avi Kivity [this message]
2009-08-04 14:16 ` Peter Zijlstra
2009-08-04 15:07 ` Martin Schwidefsky
2009-08-04 16:26 ` Peter Zijlstra
2009-08-04 17:29 ` Martin Schwidefsky
2009-08-04 17:33 ` Peter Zijlstra
2009-08-04 18:12 ` Martin Schwidefsky
2009-08-04 22:23 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46CAE096.4060606@qumranet.com \
--to=avi@qumranet.com \
--cc=Laurent.Vivier@bull.net \
--cc=jeremy@goop.org \
--cc=john@stoffel.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox