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>,
virtualization <virtualization@lists.linux-foundation.org>,
cotte@de.ibm.com
Subject: Re: [kvm-devel] [PATCH 0/2][KVM] guest time accounting
Date: Mon, 13 Aug 2007 17:19:49 +0300 [thread overview]
Message-ID: <46C06885.3020908@qumranet.com> (raw)
In-Reply-To: <200708131615.42643.borntraeger@de.ibm.com>
Christian Borntraeger wrote:
> Am Montag, 13. August 2007 schrieb Laurent Vivier:
>
>>> [copying Ingo and Rusty]
>>>
>
> @Avi, seems that sourceforge is mangling the cc list?
>
>
It's not configured to do so. Can you be more specific?
>>> 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.
>>>
>> There is also a CONFIG_VIRTUALIZATION and a CONFIG_VIRT_CPU_ACCOUNTING (from
>> s390 and powerpc) Which one to use ?
>>
>
> CONFIG_VIRT_CPU_ACCOUNTING is used for the precise accouting of user,system,
> steal and irq time on these platforms and is not what you want for the on/off
> decision.
>
Ah, ok.
>> I'm wondering if we can have a more accurate accounting:
>>
>> - For the moment we add all system time since the previous entering to the
>> VCPU to the guest time (and I guess there is some real system time in
>> it ???)
>> - Perhaps we can sum nanoseconds spent in the VCPU and add it to cpustat
>> when these ns are greater than 1 ms ? (I'm trying to make something in this
>>
> way)
>
> If you look at the patch I have posted some minutes ago, I use a method
> similar to irq_enter and irq_exit to separate real system time from guest
> time.
Yes. This is orthogonal to the current accounting patch and should make
a nice extension. It's probably useful with dynamic tick where timer
interrupts can be rare.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-08-13 16:00 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 [this message]
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=46C06885.3020908@qumranet.com \
--to=avi@qumranet.com \
--cc=Laurent.Vivier@bull.net \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--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