From: Peter Zijlstra <peterz@infradead.org>
To: mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
dave@sr71.net, fweisbec@gmail.com, tglx@linutronix.de,
sgruszka@redhat.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/urgent] sched: Avoid cputime scaling overflow
Date: Thu, 2 May 2013 15:10:33 +0200 [thread overview]
Message-ID: <20130502131033.GG13837@dyad.programming.kicks-ass.net> (raw)
In-Reply-To: <tip-55eaa7c1f511af5fb6ef808b5328804f4d4e5243@git.kernel.org>
> + for (;;) {
> + /* Make sure "rtime" is the bigger of stime/rtime */
> + if (stime > rtime) {
> + u64 tmp = rtime; rtime = stime; stime = tmp;
I keep forgetting to mention we have swap(rtime, stime); that does the above.
> + }
> +
> + /* Make sure 'total' fits in 32 bits */
> + if (total >> 32)
> + goto drop_precision;
> +
> + /* Does rtime (and thus stime) fit in 32 bits? */
> + if (!(rtime >> 32))
> + break;
> +
> + /* Can we just balance rtime/stime rather than dropping bits? */
> + if (stime >> 31)
> + goto drop_precision;
> +
> + /* We can grow stime and shrink rtime and try to make them both fit */
> + stime <<= 1;
> + rtime >>= 1;
> + continue;
> +
> +drop_precision:
> + /* We drop from rtime, it has more bits than stime */
> + rtime >>= 1;
> + total >>= 1;
> }
>
> + /*
> + * Make sure gcc understands that this is a 32x32->64 multiply,
> + * followed by a 64/32->64 divide.
> + */
> + scaled = div_u64((u64) (u32) stime * (u64) (u32) rtime, (u32)total);
> return (__force cputime_t) scaled;
> }
>
prev parent reply other threads:[~2013-05-02 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 9:35 [PATCH -tip 1/4] " Stanislaw Gruszka
2013-04-30 9:35 ` [PATCH -tip 2/4] sched: Do not account bogus utime Stanislaw Gruszka
2013-05-01 10:04 ` [tip:sched/urgent] " tip-bot for Stanislaw Gruszka
2013-04-30 9:35 ` [PATCH -tip 3/4] sched: Avoid prev->stime underflow Stanislaw Gruszka
2013-05-01 10:06 ` [tip:sched/urgent] " tip-bot for Stanislaw Gruszka
2013-04-30 9:35 ` [PATCH -tip 4/4] Revert "math64: New div64_u64_rem helper" Stanislaw Gruszka
2013-05-01 10:07 ` [tip:sched/urgent] " tip-bot for Stanislaw Gruszka
2013-04-30 11:11 ` [PATCH -tip 1/4] sched: Avoid cputime scaling overflow Ingo Molnar
2013-04-30 15:14 ` [PATCH -tip 1/4 v2] " Stanislaw Gruszka
2013-05-01 10:03 ` [tip:sched/urgent] " tip-bot for Stanislaw Gruszka
2013-05-02 13:10 ` Peter Zijlstra [this message]
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=20130502131033.GG13837@dyad.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dave@sr71.net \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sgruszka@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®