From: Jan Kiszka <jan.kiszka@domain.hid>
To: Stefan Kisdaroczi <kisda@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] autostart timer, rt_timer_start/stop
Date: Thu, 29 Dec 2005 16:03:22 +0100 [thread overview]
Message-ID: <43B3FABA.4050903@domain.hid> (raw)
In-Reply-To: <43B3EAFA.2050906@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]
Stefan Kisdaroczi wrote:
> Hi,
>
> cant the timer be started by default ?
>
> The current state (2.0.1) seems to lead to the following scenario:
> 1) Every app calls rt_timer_start()
> 2) If you call rt_timer_stop you can hurt other rt-apps, so dont
> call it
> 3) As some apps dont stop the timer, check in 1) if its already running
>
> I think most apps do not care in which mode the timer is running if it is already,
> and just go on, of course you can stop and restart the timer if its a wrong state,
> but you do not know if you hurt others.
>
> Now, as i read in the other thread that the periodic timer support isnt configured by default,
> why not start the oneshot timer automatic ?
>
> Like this, a 'normal' app doesnt need to fiddle with the timer and
> an app that really cares can still call rt_timer_inquire,_stop,_start.
>
Yea, that's good that someone else brings this topic up again! :) I've
been pointing on this several times, but as we did not come to a
conclusion how to handle the system timer in a consistent way across all
skins, no one (me included...) came up with a fix of this issue so far.
The thing is that most skins start the timer during module init via some
parameter (nowadays also as a kernel boot option for compiled-in skins).
As far as I remember, only the native and the RTAI compat skin do their
own dance - the latter one has to remain compatible, ok, but the former
one should be allowed to perform smarter.
Ok, to be more concrete: autostarting the one-shot time in the absence
of periodic mode is certainly worth considering. For the other cases and
as sysfs is no option on 2.4 kernels, what about adding a /proc-exported
control mechanism for the timer mode (and period) to either the HAL or
the nucleus? Additionally, we could provide some CONFIG_xyz to set the
default mode during compile time.
Ceterum censeo rt_timer_start/stop esse delendam. ;)
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-12-29 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-29 13:56 [Xenomai-core] autostart timer, rt_timer_start/stop Stefan Kisdaroczi
2005-12-29 15:03 ` Jan Kiszka [this message]
2005-12-29 15:35 ` Philippe Gerum
2005-12-29 16:14 ` 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=43B3FABA.4050903@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=kisda@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.