From: Pavel Machek <pma@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Huge clock drift
Date: Mon, 30 May 2011 09:03:22 +0200 [thread overview]
Message-ID: <20110530070322.GA3248@domain.hid> (raw)
In-Reply-To: <4DE1078D.3090503@domain.hid>
On Sat 2011-05-28 16:32:45, Jan Kiszka wrote:
> On 2011-05-27 21:11, Gilles Chanteperdrix wrote:
> > On 05/27/2011 08:29 PM, Jonas Witt wrote:
> >> Sorry, I missed the NTP-part. I am not using NTP. Just plain timer
> >> queries on a single system.
> >>
> >> My clock source is tsc which is the same for Xenomai I suppose.
> >>
> >> I wonder how a Xenomai task, even if it occupies 50% or even 90% of a 4
> >> milliseconds time slice can interfere with the tsc. The tsc is not
> >> incremented via an interrupt, is it? But I do not know much about the
> >> inner workings of these functions.
> >
> > The problem is not the clocksource, the problem is the timer interrupt.
> > The kernel expects 1 timer tick every millisecond.
>
> Not on archs that are CONFIG_NO_HZ capable.
Umm. NO_HZ is only active while system is idle. Kernel will still
expect the periodic ticks when CPU is busy....
(I'm not sure how the compensation works; perhaps it can compensate
even while busy..)
Pavel
next prev parent reply other threads:[~2011-05-30 7:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 17:28 [Xenomai-help] Huge clock drift Jonas Witt
2011-05-27 6:40 ` Gilles Chanteperdrix
2011-05-27 14:19 ` Jonas Witt
2011-05-27 14:38 ` Gilles Chanteperdrix
2011-05-27 15:05 ` Jan Kiszka
2011-05-27 16:22 ` Gilles Chanteperdrix
2011-05-27 18:29 ` Jonas Witt
2011-05-27 19:11 ` Gilles Chanteperdrix
2011-05-28 14:32 ` Jan Kiszka
2011-05-28 22:08 ` Gilles Chanteperdrix
2011-05-29 15:38 ` Jan Kiszka
2011-05-30 7:03 ` Pavel Machek [this message]
2011-05-30 7:07 ` Jan Kiszka
2011-05-30 7:43 ` Jonas Witt
2011-05-30 7:57 ` Jan Kiszka
2011-05-30 10:31 ` Jonas Witt
2011-05-30 10:33 ` Pavel Machek
2011-05-30 12:32 ` Jonas Witt
2011-05-30 13:08 ` 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=20110530070322.GA3248@domain.hid \
--to=pma@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.