From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Martin Shepherd <mcs@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Encouraging Xenomai test results
Date: Thu, 14 May 2009 09:16:15 +0200 [thread overview]
Message-ID: <4A0BC53F.5090505@domain.hid> (raw)
In-Reply-To: <Pine.LNX.4.64.0905131634150.7706@domain.hid>
Martin Shepherd wrote:
> One thing that I don't understand is why whenever I ran my Xenomai
> test program, the Linux clock ran slow, losing about half an hour
> during the hour-long test. My realtime floating-point load task was
> designed to preempt the Linux kernel for about 3 seconds, then go to
> sleep for about 1.2 seconds, to give Adeos time to replay pending
> interrupts to the Linux kernel. Although the realtime interrupt
> strobing task was still running during the 1.2s pauses in the load
> task, it only ran for 30us every 1ms. So I am wondering why so many
> timer interrupts appear not to have been played back by Adeos? I
> didn't seen any evidence of non-timer interrupts getting lost. Is this
> perhaps a side effect of turning off X86_PM_TIMER and HPET_TIMER, and
> leaving both Linux and Xenomai sharing the sole remaining timer?
Adeos no longer plays back the missed interrupts. It only plays back one
interrupt and let Linux' lost tick compensation algorithms do the rest.
Running real-time tasks for 3 seconds without leaving Linux run is a bad
idea (it is even surprising that it works at all). For Linux to work
correctly, we usually advise people not to let real-time task run for a
period longer than Linux tick period.
--
Gilles.
next prev parent reply other threads:[~2009-05-14 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 1:15 [Xenomai-help] Encouraging Xenomai test results Martin Shepherd
2009-05-14 7:16 ` Gilles Chanteperdrix [this message]
2009-05-15 0:15 ` Martin Shepherd
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=4A0BC53F.5090505@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=mcs@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.