public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Laurent Vivier <Laurent.Vivier@bull.net>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	virtualization <virtualization@lists.linux-foundation.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [kvm-devel] [PATCH 0/2][KVM] guest time accounting
Date: Mon, 13 Aug 2007 11:01:05 +0300	[thread overview]
Message-ID: <46C00FC1.1070306@qumranet.com> (raw)
In-Reply-To: <46BC8B39.6050202@bull.net>

Laurent Vivier wrote:
> The aim of these two patches is to measure the CPU time used by a virtual
> machine. All comments are welcome... I'm not sure it's the good way to do that.
>
> [PATCH 1/2] introduce a new field, "guest", in cpustat to store the time used by
> the CPU to run virtual CPU. Modify /proc/stat to display this new field.
>
> [PATCH 2/2] modify account_system_time() to add cputime to cpustat->guest if we
> are running a VCPU. We add this cputime to  cpustat->user instead of
> cpustat->system because this part of KVM code is in fact user code although it
> is executed in the kernel. We duplicate VCPU time between guest and user to
> allow an unmodified "top(1)" to display correct value. A modified "top(1)" is
> able to display good cpu user time and cpu guest time by subtracting cpu guest
> time from cpu user time.
>   

[copying Ingo and Rusty]

The patches look good.  A couple of comments:

- perhaps the new fields should be guarded by a #ifdef CONFIG_HYPERVISOR 
(selected by CONFIG_KVM)?  that way the (minor) additional overhead is 
only incurred if it can possibly be used.  I imagine that our canine 
cousin will want to use this as well.

- I think that there is per-task accounting of user time and system 
time; that should be extended as well.



-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2007-08-13 12:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10 15:58 [PATCH 0/2][KVM] guest time accounting Laurent Vivier
2007-08-13  8:01 ` Avi Kivity [this message]
2007-08-13  8:13   ` [kvm-devel] " Laurent Vivier
2007-08-13  8:38     ` Avi Kivity
2007-08-13 13:08       ` Laurent Vivier
2007-08-13 13:22         ` Avi Kivity
2007-08-13 14:15     ` Christian Borntraeger
2007-08-13 14:19       ` Avi Kivity
2007-08-13 14:26         ` Christian Borntraeger
2007-08-13 14:37           ` Avi Kivity
2007-08-13 20:40             ` Heiko Carstens
2007-08-19  9:32               ` List stripping out cc's (was: Re: [kvm-devel] [PATCH 0/2][KVM] guest time accounting) Avi Kivity
2007-08-19 19:53                 ` List stripping out cc's Jeff Garzik
2007-08-19 20:10                   ` Avi Kivity
2007-08-13 14:05 ` [kvm-devel] [PATCH 0/2][KVM] guest time accounting Christian Borntraeger
2007-08-13 14:10   ` Avi Kivity
2007-08-13 14:22     ` Christian Borntraeger
2007-08-13 14:22   ` Laurent Vivier
2007-08-13 14:30     ` Avi Kivity
2007-08-13 14:41       ` Laurent Vivier
2007-08-13 15:22         ` Christian Borntraeger
2007-08-13 15:36           ` Laurent Vivier

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=46C00FC1.1070306@qumranet.com \
    --to=avi@qumranet.com \
    --cc=Laurent.Vivier@bull.net \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --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