All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Smolorz <smolorz@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>,
	"Cornelius Köpp" <Cornelius.Koepp@domain.hid>
Subject: Re: [Xenomai-core] latencys drifting into negative (Xenomai 2.4.2/2.4.3)
Date: Fri, 04 Apr 2008 10:23:24 +0200	[thread overview]
Message-ID: <47F5E57C.6020309@domain.hid> (raw)
In-Reply-To: <47F551AD.9030509@domain.hid>

Jan Kiszka wrote:
> Sebastian Smolorz wrote:
>> Jan Kiszka wrote:
>>> This patch may do the trick: it uses the inverted tsc-to-ns function 
>>> instead of the frequency-based one. Be warned, it is totally untested 
>>> inside Xenomai, I just ran it in a user space test program. But it 
>>> may give an idea.
>>
>> Your patch needed two minor corrections (ns instead of ts in functions 
>> xnarch_ns_to_tsc()) in order to compile. A short run (30 minutes) of 
>> latency -t1 seems to prove your bug-fix: There seems to be no drift.
> 
> That's good to hear.
> 
>> If I got your patch correctly, it doesn't make xnarch_tsc_to_ns more 
>> precise but introduces a new function xnarch_ns_to_tsc() which is also 
>> less precise than the generic xnarch_ns_to_tsc(), right?
> 
> Yes. It is now precisely the inverse imprecision, so to say. :)
> 
>> So isn't there still the danger of getting wrong values when calling 
>> xnarch_tsc_to_ns()  not in combination with xnarch_ns_to_tsc()?
> 
> Only if the user decides to implement his own conversion. Xenomai with 
> all its skins and both in kernel and user space should always run 
> through the xnarch_* path.

OK, would you commit the patch?

-- 
Sebastian


  reply	other threads:[~2008-04-04  8:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 23:26 [Xenomai-core] latencys drifting into negative (Xenomai 2.4.2/2.4.3) Cornelius Köpp
2008-04-02  3:01 ` Tomas Kalibera
2008-04-02  9:04 ` Jan Kiszka
2008-04-02 12:00   ` Sebastian Smolorz
2008-04-02 12:28     ` Jan Kiszka
2008-04-02 12:46       ` Gilles Chanteperdrix
2008-04-02 13:00         ` Sebastian Smolorz
2008-04-02 15:28           ` Sebastian Smolorz
2008-04-02 15:58       ` Sebastian Smolorz
2008-04-02 16:05         ` Gilles Chanteperdrix
2008-04-02 16:24           ` Sebastian Smolorz
2008-04-03 12:17             ` Jan Kiszka
2008-04-03 12:27               ` Gilles Chanteperdrix
2008-04-03 12:50                 ` Jan Kiszka
2008-04-03 12:52                   ` Gilles Chanteperdrix
2008-04-03 13:15               ` Sebastian Smolorz
2008-04-03 21:52                 ` Jan Kiszka
2008-04-04  8:23                   ` Sebastian Smolorz [this message]
2008-04-04 10:45                     ` Jan Kiszka
2008-04-04 13:18                       ` Gilles Chanteperdrix
2008-04-04 13:25                         ` Jan Kiszka
2008-04-04 13:32                           ` Jan Kiszka
2008-04-04 13:32                           ` Gilles Chanteperdrix
2008-04-04 13:57                             ` Jan Kiszka
2008-04-04 14:09                               ` Gilles Chanteperdrix
2008-04-04 14:33                                 ` Jan Kiszka
2008-04-04 15:48                                   ` Gilles Chanteperdrix
2008-04-04 15:52                                     ` Philippe Gerum

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=47F5E57C.6020309@domain.hid \
    --to=smolorz@domain.hid \
    --cc=Cornelius.Koepp@domain.hid \
    --cc=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.