All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Steve <sbxenomai@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Xenomai 2.5-rc2 clock_gettime bad tv_nsec value
Date: Fri, 07 Aug 2009 08:08:28 +0200	[thread overview]
Message-ID: <4A7BC4DC.70209@domain.hid> (raw)
In-Reply-To: <abaf774b0908040623w1583f930xda88c125b64394b1@domain.hid>

Steve wrote:
> Hi,
> 
> Using Xenomai 2.5-rc2 on Linux 2.6.29.4 the following code
> periodically produces a bad result:
> 
> clock_gettime(CLOCK_REALTIME, timespec);
> 
> Where it assigns a timespec.tv_nsec that is greater than 1000 million.
>  If it helps the maximum returned value that i have seen before tv_sec
> increments and tv_nsec returns to a 'safe' value is 1048044075.
> 
> This does not happen using Xenomai 2.4.8 on the same Linux kernel.
> There are some differences between the kernel config files used for my
> 2.4.8 setup and 2.5-rc2 setup, but I don't imagine that that is the
> problem.
> 
> Any thoughts?

Well, yes. Xenomai 2.5-rc2 has been modified to do the conversion 
between ticks and timespec without divisions. I am afraid in some cases 
we are wrong (essentially, we replace the division with a 
multiplication, but it is entirely possible that the result of the 
multiplication is off by one, and so when computing the remainder, we 
get a too large value). Could you apply the following patch? It will 
modify clock_gettime implementation in kernel-space to print the value 
before conversion when the bug happens. Also tell us if you are running
in periodic mode or aperiodic mode (if you do not know, then you are
running in aperiodic mode).

diff --git a/ksrc/skins/posix/clock.c b/ksrc/skins/posix/clock.c
index 553e123..63a42fa 100644
--- a/ksrc/skins/posix/clock.c
+++ b/ksrc/skins/posix/clock.c
@@ -117,7 +117,10 @@ int clock_gettime(clockid_t clock_id, struct timespec *tp)

        switch (clock_id) {
        case CLOCK_REALTIME:
-               ticks2ts(tp, xntbase_get_time(pse51_tbase));
+               cpu_time = xntbase_get_time(pse51_tbase);
+               ticks2ts(tp, cpu_time);
+               if (tp->tv_nsec > 1000000000)
+                       printk("Bad conversion, time: %llu\n", cpu_time);
                break;

        case CLOCK_MONOTONIC:


-- 
					    Gilles.


  reply	other threads:[~2009-08-07  6:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 13:23 [Xenomai-help] Xenomai 2.5-rc2 clock_gettime bad tv_nsec value Steve
2009-08-07  6:08 ` Gilles Chanteperdrix [this message]
2009-08-19  8:27   ` Steve
2009-08-19  8:40     ` Gilles Chanteperdrix
2009-08-19  9:29       ` Steve
2009-08-19  9:37         ` Gilles Chanteperdrix
2009-08-19  9:46           ` Steve
2009-08-19 12:42             ` Gilles Chanteperdrix
2009-08-20 10:45             ` Gilles Chanteperdrix
2009-08-26 15:18               ` Steve
2009-08-26 15:24                 ` Gilles Chanteperdrix

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=4A7BC4DC.70209@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=sbxenomai@domain.hid \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.