From: Shreyas B Prabhu <shreyas@linux.vnet.ibm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>, rjw@rjwysocki.net
Cc: linux-pm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
anton@samba.org, mpe@ellerman.id.au, bsingharora@gmail.com,
David.Laight@ACULAB.COM, arnd@arndb.de,
Nicolas Pitre <nicolas.pitre@linaro.org>
Subject: Re: [PATCH v3] cpuidle: Fix last_residency division
Date: Wed, 29 Jun 2016 14:29:36 +0530 [thread overview]
Message-ID: <57738DF8.3000909@linux.vnet.ibm.com> (raw)
In-Reply-To: <57737AA1.7050201@linaro.org>
>>
>> +/*
>> + * Used for calculating last_residency in usec. Optimized for case
>> + * where last_residency in nsecs is < INT_MAX/2 by using faster
>> + * approximation. Approximated value has less than 1% error.
>> + */
>> +static inline int convert_nsec_to_usec(u64 nsec)
>> +{
>> + if (likely(nsec < INT_MAX / 2)) {
>
> UINT_MAX ?
I don't think I can use UINT_MAX here since usec += usec >> 5 can
overflow. Also using INT_MAX / 2 instead of INT_MAX since potentially
usec += usec >> 5 can be negative and usec >> 10 will retain the sign bit.
>
>> + int usec = (int)nsec;
>> +
>> + usec += usec >> 5;
>> + usec = usec >> 10;
>> + return usec;
>> + } else {
>> + u64 usec = div_u64(nsec, 1000);
>> +
>> + if (usec > INT_MAX)
>> + usec = INT_MAX;
>> + return (int)usec;
>> + }
>> +}
>
Thanks,
Shreyas
next prev parent reply other threads:[~2016-06-29 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 7:06 [PATCH v3] cpuidle: Fix last_residency division Shreyas B. Prabhu
2016-06-29 7:37 ` Daniel Lezcano
2016-06-29 8:59 ` Shreyas B Prabhu [this message]
2016-06-29 15:01 ` Nicolas Pitre
2016-06-29 15:52 ` Nicolas Pitre
2016-06-30 14:20 ` Shreyas B Prabhu
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=57738DF8.3000909@linux.vnet.ibm.com \
--to=shreyas@linux.vnet.ibm.com \
--cc=David.Laight@ACULAB.COM \
--cc=anton@samba.org \
--cc=arnd@arndb.de \
--cc=bsingharora@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nicolas.pitre@linaro.org \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).