From: Jan Kiszka <jan.kiszka@domain.hid>
To: "Ignacio García Pérez" <iggarpe@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Application broken 2.3.4 ---> 2.4.0
Date: Tue, 11 Dec 2007 13:16:04 +0100 [thread overview]
Message-ID: <475E7F84.1040600@domain.hid> (raw)
In-Reply-To: <475E7CBA.7060300@domain.hid>
Ignacio García Pérez wrote:
> Ignacio García Pérez escribió:
>
> Ok, replying myself with further findings:
>
> It turns out that the following code miserably fails to set the thread
> periodic:
>
> rt_task_set_periodic(&_blink_thread, rt_timer_read(), mili2count(250));
>
> Where this actually works:
>
> rt_task_set_periodic(&_blink_thread, TM_NOW, mili2count(250));
>
> Which makes me think that rt_task_set_periodic() fails when the passed
> idate is in the past.
>
> And you may say: why the hell do you use rt_timer_read() when you can
> use TM_NOW ???
>
> Well, I think that rt_task_set_periodic should word (AND DID) both ways,
> but actually I have a very good reason to (sometimes) use an idate in
> the past: I want the blinking synchronized to the "event" as closely as
> possible. If there is a delay D from my recorded time for the event to
> the actual call to rt_task_set_periodic, I can:
>
> a) Use rt_task_set_periodic(TM_NOD)
>
> b) Use rt_task_set_periodic(recorded_time)
>
> In the first case there will be a delay of D from every period to the
> "event", while in the second case that delay will be only in the FIRST
> execution of the periodic task.
>
> Anyway, something is truly screwed up when
> rt_task_set_periodic(&_blink_thread, rt_timer_read(), mili2count(250))
> fails to make the task periodic...
That's due to the reworked timer subsystem: Starting timers (like the
periodic task timer) in the past is reported as error - up to the
application in this case. One may discuss if this case can be considered
as an undocumented API change (I haven't re-read the docs in this regard
yet).
However, what about this to resolve your issue:
while start_date < now()
start_date += period
Of course you can write this more smartly than using a loop (e.g. if you
know that already start_date + period > now()).
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2007-12-11 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 11:38 [Xenomai-help] Application broken 2.3.4 ---> 2.4.0 Ignacio García Pérez
2007-12-11 12:04 ` Ignacio García Pérez
2007-12-11 12:16 ` Jan Kiszka [this message]
2007-12-11 12:58 ` Ignacio García Pérez
2007-12-11 13:16 ` Ignacio García Pérez
2007-12-11 13:41 ` Gilles Chanteperdrix
2007-12-11 15:17 ` Ignacio García Pérez
2007-12-11 16:41 ` Gilles Chanteperdrix
[not found] ` <47624674.5070107@domain.hid>
2007-12-14 9:46 ` Gilles Chanteperdrix
2007-12-14 17:06 ` Ignacio García Pérez
2007-12-14 19:01 ` Gilles Chanteperdrix
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=475E7F84.1040600@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=iggarpe@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.