From: Christian Borntraeger <borntraeger@de.ibm.com>
To: kvm-devel@lists.sourceforge.net
Cc: "Glauber de Oliveira Costa" <glommer@gmail.com>,
"laurent.vivier@bull.net" <laurent.vivier@bull.net>,
Jeremy Fitzhardinge <jeremy@goop.org>,
John Stoffel <john@stoffel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [kvm-devel] Réf. : Re: [PATCH 0/4] Virtual Machine Time Accounting
Date: Tue, 21 Aug 2007 10:06:42 +0200 [thread overview]
Message-ID: <200708211006.42938.borntraeger@de.ibm.com> (raw)
In-Reply-To: <5d6222a80708201334q27fc6cbcr7ce6a9d7147437a2@mail.gmail.com>
Am Montag, 20. August 2007 schrieb Glauber de Oliveira Costa:
> Although I don't know KVM to a that deep level, I think it should be
> possible to keep the virtual cpus in different process (or threads),
> and take the accounting time from there. Perfectly possible to know
> the time we spent running (user time), and the time the hypervisor
> spent doing things on our behalf (system time).
I disagree here. First thing, you dont want to have the virtual cpu in a
different process than the hypervisor control code for that cpu. Otherwise
communication has to be made via IPC.
Secondly, Its not qemu/kvm that does the accouting. Its existing userspace
code like top/snmp agents and clients! etc. that would require additional
knowledge which thread is guest code.
I personally like the approach Laurent has taken. Maybe it needs some polish
and maybe we want an account_guest_time function, but in general I think he
is doing the right thing.
Christian
next prev parent reply other threads:[~2007-08-21 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 17:54 laurent.vivier
2007-08-20 20:34 ` Glauber de Oliveira Costa
2007-08-21 7:45 ` Laurent Vivier
2007-08-21 17:46 ` Glauber de Oliveira Costa
2007-08-21 8:06 ` Christian Borntraeger [this message]
2007-08-21 17:47 ` [kvm-devel] " Glauber de Oliveira Costa
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=200708211006.42938.borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=glommer@gmail.com \
--cc=jeremy@goop.org \
--cc=john@stoffel.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=laurent.vivier@bull.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
Powered by JetHome