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 16/16] KVM-GST: adjust scheduler cpu power
Date: Wed, 26 Jan 2011 10:57:51 +0100 [thread overview]
Message-ID: <1296035871.28776.1132.camel@laptop> (raw)
In-Reply-To: <1295990853.15920.37.camel@mothafucka.localdomain>
On Tue, 2011-01-25 at 19:27 -0200, Glauber Costa wrote:
> On Tue, 2011-01-25 at 22:07 +0100, Peter Zijlstra wrote:
> > On Tue, 2011-01-25 at 18:47 -0200, Glauber Costa wrote:
> > > On Tue, 2011-01-25 at 21:13 +0100, Peter Zijlstra wrote:
> > > > On Tue, 2011-01-25 at 18:02 -0200, Glauber Costa wrote:
> > > >
> > > > > I fail to see how does clock_task influence cpu power.
> > > > > If we also have to touch clock_task for better accounting of other
> > > > > stuff, it is a separate story.
> > > > > But for cpu_power, I really fail. Please enlighten me.
> > > >
> > > > static void update_rq_clock_task(struct rq *rq, s64 delta)
> > > > {
> > > > s64 irq_delta;
> > > >
> > > > irq_delta = irq_time_read(cpu_of(rq)) - rq->prev_irq_time;
> > > >
> > > > if (irq_delta > delta)
> > > > irq_delta = delta;
> > > >
> > > > rq->prev_irq_time += irq_delta;
> > > > delta -= irq_delta;
> > > > rq->clock_task += delta;
> > > >
> > > > if (irq_delta && sched_feat(NONIRQ_POWER))
> > > > sched_rt_avg_update(rq, irq_delta);
> > > > }
> > > >
> > > > its done through that sched_rt_avg_update() (should probably rename
> > > > that), it computes a floating average of time not spend on fair tasks.
> > > >
> > > It creates a dependency on CONFIG_IRQ_TIME_ACCOUNTING, though.
> > > This piece of code is simply compiled out if this option is disabled.
> >
> > We can pull this bit out and make the common bit also available for
> > paravirt.
>
> scale_rt_power() seems to do the right thing, but all the path leading
> to it seem to work on rq->clock, rather than rq->clock_task.
Not quite, see how rq->clock_task is irq_delta less than the increment
to rq->clock? You want it to be your steal-time delta less too.
> Although I do can experiment with that as well, could you please
> elaborate on what are your reasons to prefer this over than variations
> of the method I proposed?
Because I want rq->clock_task to not include steal-time.
next prev parent reply other threads:[~2011-01-26 9:57 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 18:06 [PATCH 00/16] New Proposal for steal time in KVM Glauber Costa
2011-01-24 18:06 ` [PATCH 01/16] KVM-HDR: register KVM basic header infrastructure Glauber Costa
2011-01-26 11:06 ` Avi Kivity
2011-01-26 12:13 ` Glauber Costa
2011-01-26 15:12 ` Avi Kivity
2011-01-26 15:36 ` Glauber Costa
2011-01-26 17:22 ` Anthony Liguori
2011-01-26 17:49 ` Glauber Costa
2011-01-27 12:31 ` Avi Kivity
2011-01-24 18:06 ` [PATCH 02/16] KVM-HV: KVM - KVM Virtual Memory hypervisor implementation Glauber Costa
2011-01-24 18:06 ` [PATCH 03/16] KVM-HDR: KVM Userspace registering ioctl Glauber Costa
2011-01-26 11:12 ` Avi Kivity
2011-01-26 12:14 ` Glauber Costa
2011-01-26 15:14 ` Avi Kivity
2011-01-26 15:23 ` Glauber Costa
2011-01-24 18:06 ` [PATCH 04/16] KVM-HV: " Glauber Costa
2011-01-24 18:06 ` [PATCH 05/16] KVM-HDR: Implement wallclock over KVM - KVM Virtual Memory Glauber Costa
2011-01-26 11:13 ` Avi Kivity
2011-01-26 12:20 ` Glauber Costa
2011-01-26 15:17 ` Avi Kivity
2011-01-26 15:45 ` Glauber Costa
2011-01-27 12:17 ` Avi Kivity
2011-01-24 18:06 ` [PATCH 06/16] " Glauber Costa
2011-01-24 18:06 ` [PATCH 07/16] KVM-GST: " Glauber Costa
2011-01-24 18:06 ` [PATCH 08/16] KVM-HDR: Implement kvmclock systemtime " Glauber Costa
2011-01-24 18:06 ` [PATCH 09/16] KVM-HV: " Glauber Costa
2011-01-24 18:06 ` [PATCH 10/16] KVM-GST: " Glauber Costa
2011-01-24 18:06 ` [PATCH 11/16] KVM-HDR: KVM Steal time implementation Glauber Costa
2011-01-24 23:06 ` Rik van Riel
2011-01-24 18:06 ` [PATCH 12/16] KVM-HV: " Glauber Costa
2011-01-24 23:15 ` Rik van Riel
2011-01-24 18:06 ` [PATCH 13/16] KVM-HV: KVM Steal time calculation Glauber Costa
2011-01-24 23:20 ` Rik van Riel
2011-01-24 18:06 ` [PATCH 14/16] KVM-GST: KVM Steal time registration Glauber Costa
2011-01-24 23:27 ` Rik van Riel
2011-01-24 23:31 ` Rik van Riel
2011-01-25 1:25 ` Glauber Costa
2011-01-25 1:26 ` Rik van Riel
2011-01-25 1:28 ` Glauber Costa
2011-01-24 18:06 ` [PATCH 15/16] KVM-GST: KVM Steal time accounting Glauber Costa
2011-01-24 23:33 ` Rik van Riel
2011-01-24 18:06 ` [PATCH 16/16] KVM-GST: adjust scheduler cpu power Glauber Costa
2011-01-24 18:32 ` Peter Zijlstra
2011-01-24 18:51 ` Glauber Costa
2011-01-24 19:51 ` Peter Zijlstra
2011-01-24 19:57 ` Glauber Costa
2011-01-25 20:02 ` Glauber Costa
2011-01-25 20:13 ` Peter Zijlstra
2011-01-25 20:47 ` Glauber Costa
2011-01-25 21:07 ` Peter Zijlstra
2011-01-25 21:27 ` Glauber Costa
2011-01-26 9:57 ` Peter Zijlstra [this message]
2011-01-26 15:43 ` Glauber Costa
2011-01-26 16:46 ` Peter Zijlstra
2011-01-26 16:53 ` Peter Zijlstra
2011-01-26 18:11 ` Glauber Costa
2011-01-24 19:53 ` Peter Zijlstra
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=1296035871.28776.1132.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox