From: Jan Kiszka <jan.kiszka@domain.hid>
To: Steve Deiters <SteveDeiters@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 19:13:46 +0200 [thread overview]
Message-ID: <4BF1794A.6050207@domain.hid> (raw)
In-Reply-To: <181804936ABC2349BE503168465576460EBD62C8@domain.hid>
Steve Deiters wrote:
>> Periodically setting the time is risky if timed jobs depend
>> on Xenomai's real-time clock - it may jump in all directions...
>>
>>> Any other suggestions for providing timestamps to real time
>> tasks in
>>> this case?
>> Do you just need precise timestamps from with real-time
>> tasks, or do you have to synchronize timer events of the
>> Xenomai core on an external clock?
>>
>> For the former case (precisely our scenario), we laid the
>> ground to extend Xenomai 2.5 with RT-safe syscalls to obtain
>> Linux's view on gettimeofday. It "just" needs some polishing
>> to post this for upstream.
>> Wolfgang (CC'ed) is working on this.
>
> I'm just looking to get timestamps in the real time task. At least in
> my case being able to call gettimeofday from the real time thread would
> be exactly what I need.
>
> By the way, calling gettimeofday currently within a real time thread
> seems to occasionally freeze up my whole system. I was going to make
> another post for this after I got a chance to verify some details. Has
> anyone noticed anything similar to this?
>
Yes, that's expected: If gettimeofday runs syscall-less, it tries to
read the time offset from a page which the Linux kernel updates
regularly. When user-space detects an ongoing update, it spins until
that has completed. But as Xenomai runs the task with higher priority
than the Linux update handler, you just ran into a live-lock.
Switching on the Xenomai watchdog will confirm this: It will shoot that
task, and the system will recover.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-05-17 17:13 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 [this message]
2010-05-17 18:02 ` Josh Karch
2010-05-17 18:23 ` Jan Kiszka
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=4BF1794A.6050207@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=AndreasGlatz@domain.hid \
--cc=SteveDeiters@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.