All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai core <Xenomai-core@domain.hid>
Subject: Re: [Xenomai-core] xenomai 2.5 rc1 timing computations.
Date: Tue, 28 Apr 2009 12:07:20 +0200	[thread overview]
Message-ID: <1240913240.6990.347.camel@domain.hid> (raw)
In-Reply-To: <49F69924.8070001@domain.hid>

On Tue, 2009-04-28 at 07:50 +0200, Gilles Chanteperdrix wrote:
> Hi,
> 
> currently, the situation is this:
> - the timing core uses an approximate value of the cpu frequency (using
> xnarch_llmulshft) to do conversions between tsc and ns;
> - the APIC timer reprogrammation still uses imuldiv, that is a more
> exact cpu frequency, coupled with an approximate APIC frequency
> (obtained from ipipe_request_tickdev), to do the conversion between tsc
> delays and APIC delays;
> - the posix skin uses llimd to do conversions between timespec and
> timeval structures and tsc values
> - the posix and native skins in user-space still use llimd to do
> conversions between ns and tsc (only if using tsc in user-space).
> 
> These are causes of unprecisions, I think we should fix this, though it
> is unlikely to be the cause of the high jitters observed by Vikesh with
> 2.5-rc1.
> 

Ack, we definitely should. Working on allowing userland to use
llmulshift for timing computations for the native skin here, as a first
step. For that purpose, xnsysinfo_t has just been extended to carry the
pre-scaled values needed for llmulshft. I just don't want to have to
issue a syscall for those conversions to take place.

> Regards.
> 
-- 
Philippe.




  parent reply	other threads:[~2009-04-28 10:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  5:50 [Xenomai-core] xenomai 2.5 rc1 timing computations Gilles Chanteperdrix
2009-04-28  5:52 ` Gilles Chanteperdrix
2009-04-28 10:07 ` Philippe Gerum [this message]
2009-04-28 12:21   ` Gilles Chanteperdrix
2009-04-28 13:41     ` Philippe Gerum
2009-04-28 13:45       ` Gilles Chanteperdrix
2009-04-28 14:00         ` Philippe Gerum
2009-04-29  7:52           ` Vikesh Rambaran

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=1240913240.6990.347.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=Xenomai-core@domain.hid \
    --cc=gilles.chanteperdrix@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.