From: Jan Kiszka <jan.kiszka@domain.hid>
To: Josh Karch <JKarch@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>,
"Mauerer, Wolfgang" <wolfgang.mauerer@domain.hid>,
Andreas Glatz <AndreasGlatz@domain.hid>
Subject: Re: [Xenomai-help] Question about getting system time
Date: Mon, 17 May 2010 20:23:54 +0200 [thread overview]
Message-ID: <4BF189BA.6060303@domain.hid> (raw)
In-Reply-To: <843773D242212C4882D4EDFFBF665F7F0C9F71BAFF@FW-SBS.fw.local>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
[please avoid top posting]
Josh Karch wrote:
> Jan,
>
> If no ntp server updates are made to the Linux clock, we have noticed over a week's period a drift of ten or so seconds difference between the Linux clock and the Xenomai get time function and often have to reboot our machine to resynchronize the Xenomai and Linux clocks back to less than a couple seconds difference. I was wondering if you might explain why that might happen?
I assume you are talking about an x86 platform: Normally, Linux should
run on the TSC clocksource, just like Xenomai does. To ensure that the
hardware isn't broken, Linux continuously performs runtime checks. The
preemption by Xenomai tasks my fool this check an make Linux switch to a
different clocksource. Now you have unsynchronized sources that usually
drift.
I haven't tried this with Xenomai yet but I could imagine it works just
like it does in virtual machines: Pass tsc=reliable on the kernel
command line. This disables the runtime checks, thus should take away
any reason Linux may want to switch to anything else than TSC.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-05-17 18:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 22:14 [Xenomai-help] Question about getting system time Abhijit Majumdar
2010-05-14 5:44 ` Gilles Chanteperdrix
2010-05-14 10:34 ` Andreas Glatz
2010-05-14 10:42 ` Gilles Chanteperdrix
2010-05-17 16:27 ` Steve Deiters
2010-05-17 16:52 ` Jan Kiszka
2010-05-17 17:05 ` Steve Deiters
2010-05-17 17:13 ` Jan Kiszka
2010-05-17 18:02 ` Josh Karch
2010-05-17 18:23 ` Jan Kiszka [this message]
2010-05-17 18:51 ` Thomas Lockhart
2010-05-17 22:48 ` Steve Deiters
2010-05-17 23:50 ` Gilles Chanteperdrix
2010-05-17 23:53 ` Gilles Chanteperdrix
2010-05-18 0:23 ` Steve Deiters
2010-05-18 7:04 ` Jan Kiszka
2010-05-18 7:59 ` Gilles Chanteperdrix
2010-05-18 8:38 ` Wolfgang Mauerer
2010-05-18 10:11 ` Gilles Chanteperdrix
2010-05-18 12:11 ` Wolfgang Mauerer
2010-05-18 12:41 ` Gilles Chanteperdrix
2010-05-18 14:58 ` [Xenomai-core] " Wolfgang Mauerer
2010-05-18 15:07 ` Gilles Chanteperdrix
2010-05-18 18:41 ` Gilles Chanteperdrix
2010-05-18 20:23 ` Wolfgang Mauerer
2010-05-18 21:19 ` Gilles Chanteperdrix
2010-05-18 22:09 ` Jan Kiszka
2010-05-18 22:24 ` Gilles Chanteperdrix
2010-05-18 23:02 ` Jan Kiszka
2010-05-19 5:49 ` Gilles Chanteperdrix
2010-05-19 7:11 ` Jan Kiszka
2010-05-21 8:55 ` Gilles Chanteperdrix
2010-05-27 15:35 ` Wolfgang Mauerer
2010-05-19 19:16 ` Daniele Nicolodi
2010-05-19 20:55 ` 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=4BF189BA.6060303@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=AndreasGlatz@domain.hid \
--cc=JKarch@domain.hid \
--cc=wolfgang.mauerer@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.