From: Marc Pignat <marc.pignat@hevs.ch>
To: tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, "Remy Bohmer" <l.pinguin@gmail.com>,
"David Brownell" <david-b@pacbell.net>
Subject: [BUG] clockevents : clockevent_delta2ns usage
Date: Mon, 2 Jul 2007 10:43:39 +0200 [thread overview]
Message-ID: <200707021043.39617.marc.pignat@hevs.ch> (raw)
Hello all!
We're currently working with David Brownell and Remy Bohmer on implementation
of clocksource/events on the at91rm9200 processor (arm arch).
While debugging our implementation, we came about a rounding problem, in the
setting of min_delta_ns field, and I think it can be in almost all clock_event_device.
Almost all clock_event_device initialize the field min_delta_ns this way:
clkevt32k.mult = div_sc(CLOCK_TICK_RATE, NSEC_PER_SEC, clkevt32k.shift);
clkevt32k.max_delta_ns = clockevent_delta2ns(0x000fffff, &clkevt32k);
clkevt32k.min_delta_ns = clockevent_delta2ns(1, &clkevt32k);
The clockevent_delta2ns function rounds the result down, so the rounded min_delta_ns
can be smaller than the real min_delta_ns.
When clockevents_program_event is called, this rounding problem shows up:
...
if (delta < dev->min_delta_ns)
delta = dev->min_delta_ns;
clc = delta * dev->mult;
clc >>= dev->shift;
return dev->set_next_event((unsigned long) clc, dev)
When delta is to small, min_delta_ns will be used, and with a wrong rounding,
will call set_next_event with a value smaller than the expected, and
set_next_event will fail.
This will result in an infinite loop when clockevents_program_event is called
from tick_program_event with a too short delay.
In our driver, we fixed this problem using that:
- clkevt32k.min_delta_ns = clockevent_delta2ns(1, &clkevt32k);
+ clkevt32k.min_delta_ns = clockevent_delta2ns(1, &clkevt32k)+1;
I think other clock_event_device can have the same problem.
Regards
Marc
next reply other threads:[~2007-07-02 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 8:43 Marc Pignat [this message]
2007-07-02 16:42 ` David Brownell
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=200707021043.39617.marc.pignat@hevs.ch \
--to=marc.pignat@hevs.ch \
--cc=david-b@pacbell.net \
--cc=l.pinguin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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®