From: Peter Zijlstra <peterz@infradead.org>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
aliguori@us.ibm.com, Rik van Riel <riel@redhat.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH v2 5/6] KVM-GST: adjust scheduler cpu power
Date: Tue, 01 Feb 2011 17:19:28 +0100 [thread overview]
Message-ID: <1296577168.26581.240.camel@laptop> (raw)
In-Reply-To: <1296575996.5081.20.camel@mothafucka.localdomain>
On Tue, 2011-02-01 at 13:59 -0200, Glauber Costa wrote:
>
> Because that part is kvm-specific, and this is scheduler general.
> It seemed cleaner to me to do it this way. But I can do it differently,
> certainly.
Well, any steal time clock will be hypervisor specific, but if we agree
that anything that enables CONFIG_PARAVIRT_TIME_ACCOUNTING provides a
u64 steal_time_clock(int cpu) function then all should be well, right?
The bit you have in kvm is almost that, except it assumes cpu ==
this_cpu.
You simply cannot rely on the silly tick accounting to drive any clock,
its archaic.
next prev parent reply other threads:[~2011-02-01 16:18 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 19:52 [PATCH v2 0/6] KVM Steal time, new submission Glauber Costa
2011-01-28 19:52 ` [PATCH v2 1/6] KVM-HDR: KVM Steal time implementation Glauber Costa
2011-01-29 1:28 ` Rik van Riel
2011-01-28 19:52 ` [PATCH v2 2/6] KVM-HV: " Glauber Costa
2011-01-29 1:46 ` Rik van Riel
2011-01-30 13:13 ` Avi Kivity
2011-02-01 15:48 ` Glauber Costa
2011-02-01 17:09 ` Avi Kivity
2011-02-01 19:58 ` Glauber Costa
2011-02-02 10:09 ` Avi Kivity
2011-01-31 11:07 ` Peter Zijlstra
2011-01-28 19:52 ` [PATCH v2 3/6] KVM-GST: KVM Steal time accounting Glauber Costa
2011-01-29 1:16 ` Jeremy Fitzhardinge
2011-01-29 1:27 ` Glauber Costa
2011-01-29 1:53 ` Rik van Riel
2011-01-30 14:04 ` Avi Kivity
2011-01-30 16:45 ` lidong chen
2011-02-01 15:58 ` Glauber Costa
2011-02-01 15:57 ` Glauber Costa
2011-02-02 10:11 ` Avi Kivity
2011-02-02 10:51 ` Avi Kivity
2011-02-02 11:57 ` Glauber Costa
2011-01-28 19:52 ` [PATCH v2 4/6] KVM-GST: KVM Steal time registration Glauber Costa
2011-01-29 2:16 ` Rik van Riel
2011-01-30 13:16 ` Avi Kivity
2011-02-01 15:53 ` Glauber Costa
2011-02-01 16:17 ` Peter Zijlstra
2011-02-01 17:00 ` Glauber Costa
2011-02-01 17:44 ` Peter Zijlstra
2011-02-01 20:20 ` Venkatesh Pallipadi
2011-01-31 11:11 ` Peter Zijlstra
2011-01-28 19:52 ` [PATCH v2 5/6] KVM-GST: adjust scheduler cpu power Glauber Costa
2011-01-31 11:25 ` Peter Zijlstra
2011-01-31 11:27 ` Peter Zijlstra
2011-02-01 15:59 ` Glauber Costa
2011-02-01 16:19 ` Peter Zijlstra [this message]
2011-02-01 16:22 ` Glauber Costa
2011-02-01 18:59 ` Peter Zijlstra
2011-02-01 19:55 ` Glauber Costa
2011-02-01 20:04 ` Peter Zijlstra
2011-01-28 19:52 ` [PATCH v2 6/6] Describe KVM_MSR_STEAL_TIME Glauber Costa
2011-01-30 13:19 ` Avi Kivity
2011-02-01 15:54 ` Glauber Costa
2011-02-02 10:14 ` Avi Kivity
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=1296577168.26581.240.camel@laptop \
--to=peterz@infradead.org \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.