All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jeff Weber <jwamsc@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] CLOCK_REALTIME synchronized to NTP
Date: Thu, 31 Mar 2011 00:00:25 +0200	[thread overview]
Message-ID: <4D93A7F9.8060108@domain.hid> (raw)
In-Reply-To: <AANLkTikiEN7Pd-F2FqgXf9MGSTqg1wq_KxsumfZeR5xX@mail.gmail.com>

Jeff Weber wrote:
> On Wed, Mar 23, 2011 at 2:37 AM, Gilles Chanteperdrix <
> gilles.chanteperdrix@xenomai.org> wrote:
> 
>> Jeff Weber wrote:
>>> I need to timetag events from a realtime context with a NPT-synchronized
>>> system clock.  This topic comes up periodically on the mailing list.
>>  Last I
>>> recall, there was talk of adding the capability via an alternate
>>> (non-CLOCK_REALTIME) clock_id. What is the status of this topic?
>> The CLOCK_HOST_REALTIME is available in the xenomai-head branch (to be
>> 2.6 branch, soon). It requires modifications of the I-pipe patch which
>> are available, at least, on x86, but are probably not really hard to
>> implement on other platforms.
>>
> 
>  clock_gettime(CLOCK_HOST_REALTIME) fails when called from kernel, and from
> clocktest.  Any ideas why?
> Does the CLOCK_HOST_REALTIME need to be initialized in some way?
> Test and config follow.
> 
> TIA,
> Jeff
> 
> 
> 
> # /usr/xenomai/bin/clocktest -D -C 42
> hostrt data area is not live
> clock_gettime failed for clock id 42
> hostrt data area is not live
> 
> # grep -rw CLOCK_HOST_REALTIME /usr/xenomai/include/
> /usr/xenomai/include/posix/time.h:#define CLOCK_HOST_REALTIME 42
> 
>  # zgrep HOSTRT /proc/config.gz
> CONFIG_XENO_OPT_HOSTRT=y
> CONFIG_HAVE_IPIPE_HOSTRT=y
> 
> # cat /proc/xenomai/version
> 2.5.90
> 
> # cat /proc/ipipe/version
> 2.9-00
> 
> # uname -r
> 2.6.37.3-xeno-head-smp
> 
> Architecture is x86 32-bit SMP with TSC.

CLOCK_HOST_REALTIME will work, only if the Linux kernel also uses the
TSC as its clocksource. So, check the "Switching to clocksource"
messages, or "disabling.*tsc" in the kernel log to see if the kernel has
not decided to use another clock source.

-- 
                                                                Gilles.


  reply	other threads:[~2011-03-30 22:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  0:59 [Xenomai-help] CLOCK_REALTIME synchronized to NTP Jeff Weber
2011-03-23  7:34 ` Jan Kiszka
2011-03-23  7:37 ` Gilles Chanteperdrix
2011-03-30 21:56   ` Jeff Weber
2011-03-30 22:00     ` Gilles Chanteperdrix [this message]
2011-03-30 22:05       ` Jeff Weber
2011-03-30 22:19         ` Gilles Chanteperdrix
2011-03-30 22:40           ` Gilles Chanteperdrix
2011-03-30 23:19             ` 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=4D93A7F9.8060108@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jwamsc@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.