From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: ZIV-Alberto Ozalla Cantabrana <alberto.ozalla@cgglobal.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] rt_task_sleep_until() miss release point?
Date: Thu, 6 Nov 2014 16:37:38 +0100 [thread overview]
Message-ID: <20141106153738.GC30908@sisyphus.hd.free.fr> (raw)
In-Reply-To: <545B9297.2090003@cgglobal.com>
On Thu, Nov 06, 2014 at 03:24:08PM +0000, ZIV-Alberto Ozalla Cantabrana wrote:
> Hi all,
>
> enclosed you will find two examples:
>
> * rt_task_sleep_until() missing release point, and
> * rt_task_sleep_until() working fine.
>
> In the first example:
>
> Current time: t1=4205571 ms - Calculated next release point: t2= 4205572 ms
> Real release: t3=4205574 ms
>
> Many Thanks
> Alberto Ozalla
>
> Simplest example that shows the issue:
When you post an example, please post a "self contained" one, i.e.
one that can be compiled and run without:
- any missing code or ellipses
- references to functions not contained in the code or xenomai
librairies, such as cu_log.
> #1 SMP 20<6>kernel: [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
You do not need CONFIG_SMP on an uniprocessor, this adds some
overhead. The overhead is mitigated on Xenomai 3, but not on xenomai
2.x.
--
Gilles.
next prev parent reply other threads:[~2014-11-06 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 15:24 [Xenomai] rt_task_sleep_until() miss release point? ZIV-Alberto Ozalla Cantabrana
2014-11-06 15:37 ` Gilles Chanteperdrix [this message]
2014-11-06 15:52 ` ZIV-Alberto Ozalla Cantabrana
2014-11-06 15:55 ` Gilles Chanteperdrix
2014-11-06 16:46 ` ZIV-Alberto Ozalla Cantabrana
2014-11-06 20:22 ` Philippe Gerum
2014-11-07 9:25 ` ZIV-Alberto Ozalla Cantabrana
2014-11-07 9:37 ` Gilles Chanteperdrix
2014-11-07 9:42 ` 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=20141106153738.GC30908@sisyphus.hd.free.fr \
--to=gilles.chanteperdrix@xenomai.org \
--cc=alberto.ozalla@cgglobal.com \
--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.