From: Avi Kivity <avi@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Glauber Costa <glommer@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Rik van Riel <riel@redhat.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Eric B Munson <emunson@mgebm.net>, Jeff Law <law@redhat.com>
Subject: Re: [PATCH v4 8/9] KVM-GST: adjust scheduler cpu power
Date: Sun, 03 Jul 2011 16:20:27 +0300 [thread overview]
Message-ID: <4E106C9B.6020403@redhat.com> (raw)
In-Reply-To: <1309602291.10073.22.camel@twins>
On 07/02/2011 01:24 PM, Peter Zijlstra wrote:
> static void update_rq_clock_task(struct rq *rq, s64 delta)
> {
> s64 irq_delta = 0, steal = 0;
>
> rq->clock_task += delta;
>
> if ((irq_delta + steal)&& sched_feat(NONTASK_POWER))
> sched_rt_avg_update(rq, irq_delta + steal);
> }
>
> And we want it to emit the equivalent of:
>
> static void update_rq_clock_task(struct rq *rq, s64 delta)
> {
> rq->clock_task += delta;
> }
>
> Now Glauber is properly paranoid and doesn't trust his compiler (this is
> very hot code in the kernel so any extra code emitted here is sad) and
> chose the heavy handed CPP solution.
>
> Now without checking a all relevant gcc versions on all relevant
> architectures (see you in a few weeks etc..) can we actually rely on gcc
> doing such relatively simple things correct, or should we stick with CPP
> just to make sure?
I'm pretty sure any relevant version of gcc will do the right optimizations.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-07-03 13:20 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 [this message]
2011-07-02 10:31 ` Peter Zijlstra
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=4E106C9B.6020403@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=emunson@mgebm.net \
--cc=glommer@redhat.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=kvm@vger.kernel.org \
--cc=law@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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.