From: Philippe Gerum <rpm@xenomai.org>
To: Tobias Marschall <tmarscha@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] some questions about alarms
Date: Sat, 22 Apr 2006 12:08:10 +0200 [thread overview]
Message-ID: <444A008A.7000100@domain.hid> (raw)
In-Reply-To: <200604211711.44211.tmarscha@domain.hid>
Tobias Marschall wrote:
> Hello,
>
> my application needs (besides doing some other stuff) to set some output
> signals on an interface card at specific points in time. I think such a
> simple thing doesn't deserve its own thread and am considering to use alarms
> for this.
>
> Is it correct that the handler of an alarm is executed with the same priority
> as the thread that created it? Meaning that the alarm execution will be
> delayed if a higher-priority (primary mode) thread is running at the time the
> alarm expires?
>
Alarms used in kernel context are run on behalf of the Xenomai timer ISR
context. In user-space, real-time alarms are currently handled by server
threads you create, which call the rt_alarm_wait() service to wait for
the next alarm shot, then process the timeout from their own context. As
a side-effect, this service boosts the calling thread priority above all
regular Xenomai threads, i.e. to some kind of pseudo-interrupt level.
> In my case it would be most convenient to be able to program an alarm timer
> using an absolute time (date). I didn't find such a function in the API
> documentation (native skin). Is the absense of such a function intended or
> did simply nobody implement it? Is it possible to implement such a function
> by just modifying the native skin?
>
Yes, but I don't think that alarms are the most appropriate feature to
use in your case. Alarms are basically provided for setting watchdogs
that would handle timeout conditions.
> But perhaps there is a better way to solve my issue. Is there any "best
> practice" for my problem? By now I see to possibilities: 1) Use a
> rt_timer_read in connection with alarms. 2) Spawn a whole thread and use
> rt_task_sleep_until.
>
Spawning a thread and use rt_task_set_periodic()+rt_task_wait_period()
would be better here. You would be able to specify an absolute starting
date, and a fixed period.
> Any Ideas?
>
> Best regards and thanks in advance,
> Tobias
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>
--
Philippe.
prev parent reply other threads:[~2006-04-22 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 15:11 [Xenomai-help] some questions about alarms Tobias Marschall
2006-04-22 10:08 ` Philippe Gerum [this message]
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=444A008A.7000100@domain.hid \
--to=rpm@xenomai.org \
--cc=tmarscha@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.