From: Guenter Roeck <linux@roeck-us.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Pekka Enberg <penberg@kernel.org>,
Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Jean Delvare <khali@linux-fr.org>,
lm-sensors@lm-sensors.org
Subject: Re: [PATCH v4] linux/kernel.h: Fix DIV_ROUND_CLOSEST to support negative dividends
Date: Fri, 31 Aug 2012 14:05:57 -0700 [thread overview]
Message-ID: <20120831210557.GA3645@roeck-us.net> (raw)
In-Reply-To: <20120831123812.62729e1c.akpm@linux-foundation.org>
On Fri, Aug 31, 2012 at 12:38:12PM -0700, Andrew Morton wrote:
> On Fri, 31 Aug 2012 08:02:19 -0700
> Guenter Roeck <linux@roeck-us.net> wrote:
>
> > DIV_ROUND_CLOSEST returns a bad result for negative dividends:
> > DIV_ROUND_CLOSEST(-2, 2) = 0
> >
> > Most of the time this does not matter. However, in the hardware monitoring
> > subsystem, DIV_ROUND_CLOSEST is sometimes used on integers which can be
> > negative (such as temperatures).
> >
> > ...
> >
> > +
> > +/*
> > + * Divide positive or negative dividend by positive divisor and round
> > + * to closest integer. Result is undefined for negative divisors.
> > + */
> > #define DIV_ROUND_CLOSEST(x, divisor)( \
> > { \
> > - typeof(divisor) __divisor = divisor; \
> > - (((x) + ((__divisor) / 2)) / (__divisor)); \
> > + typeof(x) __x = x; \
> > + typeof(divisor) __d = divisor; \
> > + (((typeof(x))-1) >= 0 || (__x) >= 0) ? \
> > + (((__x) + ((__d) / 2)) / (__d)) : \
> > + (((__x) - ((__d) / 2)) / (__d)); \
> > } \
>
> Looks good to me. The patch causes no change in text size for
> kernel/sched/fair.o and drivers/cpuidle/governors/menu.o, so it seems
> that the cc trickery is working.
>
> I'll add it to my tree for testing - please merge this via your tree.
>
Will do.
Thanks,
Guenter
next prev parent reply other threads:[~2012-08-31 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 15:02 Guenter Roeck
2012-08-31 19:38 ` Andrew Morton
2012-08-31 21:05 ` Guenter Roeck [this message]
2012-09-01 17:02 ` Jean Delvare
2012-09-02 2:14 ` Guenter Roeck
2012-09-09 14:57 ` Geert Uytterhoeven
2012-09-09 16:17 ` Guenter Roeck
2012-09-09 20:38 ` Geert Uytterhoeven
2012-09-09 21:30 ` Guenter Roeck
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=20120831210557.GA3645@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mingo@kernel.org \
--cc=penberg@kernel.org \
/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
Powered by JetHome