public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: kvm-devel@lists.sourceforge.net,
	Laurent Vivier <Laurent.Vivier@bull.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] [PATCH 0/2][KVM] guest time accounting
Date: Mon, 13 Aug 2007 17:10:00 +0300	[thread overview]
Message-ID: <46C06638.6010108@qumranet.com> (raw)
In-Reply-To: <200708131605.40479.borntraeger@de.ibm.com>

Christian Borntraeger wrote:
> Am Freitag, 10. August 2007 schrieb Laurent Vivier:
>   
>> 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.
>
> I did something similar for or s390guest prototype, that Carsten posted in 
> May.  I decided to account guest time to the user process instead of adding a 
> new field to avoid hazzle with old top. As you can read in the patch comment, 
> I personally prefer a new field if we can get one.
>   

Laurent's patch gives the best of both worlds: on old 'top', you get 
guest time accounted as user time, while on new 'top' it is accounted 
separately.  This is done by reporting user time as the sum of the real 
user time and guest time.  A newer 'top' can subtract guest time from 
user time to get the correct statistic.


> My implementation uses a similar mechanism like hard and softirq. So I have an 
> sie_enter an sie_exit and a task_is_in_sie function - like irq_enter and 
> irq_exit. The main difference is based on the fact, that s390 has precise 
> accouting for irq, steal, user and system time, and therefore my patch is 
> based on architecture specifc code using CONFIG_VIRT_CPU_ACCOUNT. 
>   

Okay, so the code should be under that config option, and kvm should 
select it.


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


  reply	other threads:[~2007-08-13 15:49 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 ` [kvm-devel] " Avi Kivity
2007-08-13  8:13   ` 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 [this message]
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=46C06638.6010108@qumranet.com \
    --to=avi@qumranet.com \
    --cc=Laurent.Vivier@bull.net \
    --cc=borntraeger@de.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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