From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: __timer_udelay(1) may return immediately
Date: Thu, 02 Apr 2015 11:31:29 +0200 [thread overview]
Message-ID: <551D0C71.8050707@free.fr> (raw)
Hello everyone,
I'm using timer-based delays from arch/arm/lib/delay.c
Consider the following configuration:
HZ=100
timer->freq = 1000000
Thus
UDELAY_MULT = 107374
ticks_per_jiffy = 10000
Thus __timer_udelay(1) =>
__timer_const_udelay(107374) =>
__timer_delay(0) => calls get_cycles() twice then returns prematurely
The issue comes from a tiny rounding error as
107374 * ticks_per_jiffy >> UDELAY_SHIFT = 0,9999983
which is rounded down to 0.
The root of the issue is that mathematically,
UDELAY_MULT = 2199023 * HZ / 2048 = 107374,169921875
which is rounded down to 107374.
It seems to me that a simple solution would be to round
UDELAY_MULT up instead of down.
Thus UDELAY_MULT = 107375
107375 * ticks_per_jiffy >> UDELAY_SHIFT = 1,0000076
We might end up sleeping one cycle more than necessary, but I don't
think spinning a bit longer would be a problem?
Patch provided for illustration purposes.
What do you think?
Regards.
diff --git a/arch/arm/include/asm/delay.h b/arch/arm/include/asm/delay.h
index dff714d..873a43e 100644
--- a/arch/arm/include/asm/delay.h
+++ b/arch/arm/include/asm/delay.h
@@ -10,7 +10,7 @@
#include <asm/param.h> /* HZ */
#define MAX_UDELAY_MS 2
-#define UDELAY_MULT ((UL(2199023) * HZ) >> 11)
+#define UDELAY_MULT (((UL(2199023) * HZ) >> 11) + 1)
#define UDELAY_SHIFT 30
#ifndef __ASSEMBLY__
--
(Note to self: tangentially relevant discussion)
http://thread.gmane.org/gmane.linux.kernel/1858260
next reply other threads:[~2015-04-02 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 9:31 Mason [this message]
2015-04-02 12:12 ` __timer_udelay(1) may return immediately Mason
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=551D0C71.8050707@free.fr \
--to=slash.tmp@free.fr \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).