From: Peter Zijlstra <peterz@infradead.org>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Rik van Riel <riel@redhat.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
Avi Kivity <avi@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Eric B Munson <emunson@mgebm.net>
Subject: Re: [PATCH v4 8/9] KVM-GST: adjust scheduler cpu power
Date: Sat, 02 Jul 2011 12:31:22 +0200 [thread overview]
Message-ID: <1309602682.10073.25.camel@twins> (raw)
In-Reply-To: <1309555369-16867-9-git-send-email-glommer@redhat.com>
On Fri, 2011-07-01 at 17:22 -0400, Glauber Costa wrote:
> This patch makes update_rq_clock() aware of steal time.
> The mechanism of operation is not different from irq_time,
> and follows the same principles. This lives in a CONFIG
> option itself, and can be compiled out independently of
> the rest of steal time reporting. The effect of disabling it
> is that the scheduler will still report steal time (that cannot be
> disabled), but won't use this information for cpu power adjustments.
>
> Everytime update_rq_clock_task() is invoked, we query information
> about how much time was stolen since last call, and feed it into
> sched_rt_avg_update().
>
> Although steal time reporting in account_process_tick() keeps
> track of the last time we read the steal clock, in prev_steal_time,
> this patch do it independently using another field,
> prev_steal_time_rq. This is because otherwise, information about time
> accounted in update_process_tick() would never reach us in update_rq_clock().
>
> Signed-off-by: Glauber Costa <glommer@redhat.com>
> CC: Rik van Riel <riel@redhat.com>
> CC: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> CC: Peter Zijlstra <peterz@infradead.org>
> CC: Avi Kivity <avi@redhat.com>
> CC: Anthony Liguori <aliguori@us.ibm.com>
> CC: Eric B Munson <emunson@mgebm.net>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cleaning up that CPP mess when the GCC people come back saying their
compiler will properly do that optimization can always be done in a
follow up patch.
Thanks!
next prev parent reply other threads:[~2011-07-02 10:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 21:22 [PATCH v4 0/9] Steal time series again Glauber Costa
2011-07-01 21:22 ` [PATCH v4 1/9] introduce kvm_read_guest_cached Glauber Costa
2011-07-01 21:22 ` [PATCH v4 2/9] KVM-HDR Add constant to represent KVM MSRs enabled bit Glauber Costa
2011-07-01 21:22 ` [PATCH v4 3/9] KVM-HDR: KVM Steal time implementation Glauber Costa
2011-07-01 21:22 ` [PATCH v4 4/9] KVM-HV: " Glauber Costa
2011-07-01 21:22 ` [PATCH v4 5/9] KVM-GST: Add a pv_ops stub for steal time Glauber Costa
2011-07-01 21:22 ` [PATCH v4 6/9] add jump labels for ia64 paravirt Glauber Costa
2011-07-01 21:22 ` [PATCH v4 7/9] KVM-GST: KVM Steal time accounting Glauber Costa
2011-07-02 10:30 ` Peter Zijlstra
2011-07-01 21:22 ` [PATCH v4 8/9] KVM-GST: adjust scheduler cpu power Glauber Costa
2011-07-02 10:24 ` Peter Zijlstra
2011-07-03 13:20 ` Avi Kivity
2011-07-02 10:31 ` Peter Zijlstra [this message]
2011-07-01 21:22 ` [PATCH v4 9/9] KVM-GST: KVM Steal time registration Glauber 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=1309602682.10073.25.camel@twins \
--to=peterz@infradead.org \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=emunson@mgebm.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox