All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Synchronising TSC and periodic timer
Date: Wed, 15 Mar 2006 08:24:58 +0100	[thread overview]
Message-ID: <4417C14A.2010900@domain.hid> (raw)
In-Reply-To: <44172B67.2000609@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

Jan Kiszka wrote:
> Hi,
> 
> for those who haven't followed the endless "RTDM and Timer functions"
> thread: we are currently discussing a way to provide high-resolution
> timestamps in periodic mode for RTDM users. It was suggested to use the
> TSC for this, but I noted that this source will not be in sync with the
> periodic system timer and may even be out of sync across multiple CPUs.
> 
> A straight-forward approach to overcome this might be to record the
> current TSC value together with the current jiffies in
> xntimer_do_tick_periodic(). This tuple (per CPU) could then be provided
> to skin implementers in order to let them offer a high-resolution
> timestamp source even in periodic mode. Hmm, sounds too simple actually,
> so I'm waiting now for someone pointing out the pitfalls.

Likely too simple: The periodic IRQ seems to pop up on every CPU so that
the TSC could be recorded, but will this happen synchronously? At least
we will see (IRQ) jitters, and those jitters could already create in the
single-CPU case a non-monotonic clock...

Does anyone ever studied if and how Linux synchronises across CPUs?
There was some activity around the problematic AMD64 multicores, but I
haven't looked at the details and if it's actually solved now.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2006-03-15  7:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14 20:45 [Xenomai-core] Synchronising TSC and periodic timer Jan Kiszka
2006-03-15  7:24 ` Jan Kiszka [this message]
     [not found]   ` <4417C74D.3060203@domain.hid>
2006-03-15  8:14     ` Jan Kiszka
2006-03-15 12:59   ` Philippe Gerum
2006-03-15 13:26     ` Gilles Chanteperdrix
2006-03-15 22:58       ` Philippe Gerum
2006-03-20 11:48         ` Jan Kiszka
2006-03-20 13:26           ` Philippe Gerum
2006-03-20 14:42             ` Rodrigo Rosenfeld Rosas
2006-03-20 16:51               ` Philippe Gerum
2006-03-20 19:27                 ` Rodrigo Rosenfeld Rosas
2006-03-21  0:11                   ` Jan Kiszka
2006-03-21  3:11                     ` Rodrigo Rosenfeld Rosas
2006-03-20 14:46             ` Jan Kiszka
2006-03-21 12:44               ` Philippe Gerum
2006-03-24 13:14                 ` Jan Kiszka
     [not found]             ` <200603201137.12548.rosenfeld@domain.hid>
2006-03-20 15:23               ` Philippe Gerum
2006-03-20 19:01                 ` Rodrigo Rosenfeld Rosas
2006-03-21 17:57                   ` Philippe Gerum
2006-03-15 13:34   ` Gilles Chanteperdrix
2006-03-15 16:50     ` Jan Kiszka
2006-03-16 15:26       ` Gilles Chanteperdrix
2006-03-17  1:16         ` Jan Kiszka
     [not found] <1CFEB358338412458B21FAA0D78FE86D02CABF1C@rennsmail02.eu.thmulti.com>
2006-03-15 17:20 ` Jan Kiszka

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=4417C14A.2010900@domain.hid \
    --to=jan.kiszka@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.