From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [RFC] Fix excessive host tick latencies
Date: Fri, 30 Apr 2010 23:01:18 +0200 [thread overview]
Message-ID: <4BDB451E.6010109@domain.hid> (raw)
In-Reply-To: <1272658402.24705.108.camel@domain.hid>
Philippe Gerum wrote:
> On Fri, 2010-04-30 at 15:33 +0200, Jan Kiszka wrote:
>> Hi Philippe,
>>
>> I'm not 100% sure if this plugs all remaining wholes in the deferred
>> host tick processing, but at least the most easiest reproducible one is
>> cured now for me (Linux latency peak after termination of 'latency').
>> Please let me know if you see more potential issues, otherwise I would
>> include this in my for-upstream queue.
>
> That patch is correct, please queue it. Anything that breaks the
> assumption described in the following comment from
> xntimer_next_local_shot() is wrong wrt tick deferral: "The host tick
> deferral is cleared whenever Xenomai is about to yield control to the
> host kernel".
>
> In short, when the code will match the comments and documentation, we
> will be done with debugging.
What I meant is that with the nucleus debugging fixed, we may not even
enter __xnpod_schedule often enough to handle the host tick propagation.
So, maybe we should make xnpod_schedule call __xnpod_schedule if XNHTICK
or XNHDEFER are set.
--
Gilles.
next prev parent reply other threads:[~2010-04-30 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 13:33 [Xenomai-core] [RFC] Fix excessive host tick latencies Jan Kiszka
2010-04-30 14:29 ` Gilles Chanteperdrix
2010-04-30 14:34 ` Jan Kiszka
2010-04-30 20:13 ` Philippe Gerum
2010-04-30 21:01 ` Gilles Chanteperdrix [this message]
2010-05-01 8:24 ` 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=4BDB451E.6010109@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=rpm@xenomai.org \
--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.