All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: rpm@xenomai.org
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH-STACK] more timer rework, group-based	access control
Date: Sat, 30 Jun 2007 07:56:09 +0200	[thread overview]
Message-ID: <4685F079.7090202@domain.hid> (raw)
In-Reply-To: <1183151844.6574.157.camel@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 2623 bytes --]

Philippe Gerum wrote:
>> rt-caps-group.patch
> 
> Good idea, but totally untested on my side (did I already mention my
> laziness?). Will merge and backport to 2.3.x, XENO_OPT_SECURITY_ACCESS
> was too cheap to be good anyway.

What about moving that scheduling parameter settings into the
trampoline? Some legacy RTOS libs would still have to be adapted.

> 
>> -----------------------------------
>>
>> See dedicated posts earlier on this list.
>>
>>
>> refactor-timer-modes.patch
>> --------------------------
>>
>> xntimers are now of three kinds: XNTM_MONOREL, XNTM_MONOABS, or
>> XNTM_REALABS. This mode is passed on xntimer_start or on invocation of
>> higher services (xnpod_suspend_thread e.g.). Users were widely
>> automatically converted and may lack optimisation for the new scheme.
>> Please review carefully for regressions!
>>
> 
> The only reason for me to whine about this one so far concerns naming
> issues. Why do things need to be that picky?
> 
> I mean, we have only three modes, relative, absolute monotonic and
> absolute realtime and we discussed in great length why we won't have
> more than those. Given that "relative non-monotonic" would make no sense
> here, and that "realtime" carries a strong notion of absoluteness in
> relation to the wallclock, let's keep "relative", "absolute" and
> "realtime". In any case, "mono" is not widespread enough for people to
> immediately catch "monotonic" anyway, so in case of doubt: I'd say
> _RTFM_.
> 
> Additionally, having XN_INFINITE and XNTM_RELATIVE/ABSOLUTE/REALTIME is
> a clear sign of discrepancy. Please, keep my laziness intact, and let's
> keep XN_ for general macros. I know that this is somehow in
> contradiction with the current practice for the native skin, but I'm
> full of contradictions anyway, so...

Hmm, everything has it's pros and cons, but mostly you are right. Here
is a new proposal, please tell me if it's acceptable so that I can
rebase the rest:

--- xenomai.orig/include/nucleus/types.h
+++ xenomai/include/nucleus/types.h
@@ -62,8 +62,13 @@ typedef int (*xniack_t)(unsigned irq);

 #define XN_INFINITE   (0)
 #define XN_NONBLOCK   ((xnticks_t)-1)
-#define XN_RELATIVE   0
-#define XN_ABSOLUTE   1
+
+/* Timer modes */
+typedef enum xntmode {
+       XN_RELATIVE,
+       XN_ABSOLUTE,
+       XN_REALTIME
+} xntmode_t;

 #define XN_APERIODIC_TICK  0
 #define XN_NO_TICK         ((xnticks_t)-1)


Last issue pending is the xintr locking thing. Will try to have a closer
look again and kick Dmitry for some more explanations of his patch.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2007-06-30  5:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 17:06 [Xenomai-core] [PATCH-STACK] more timer rework, group-based access control Jan Kiszka
2007-06-29 21:17 ` Philippe Gerum
2007-06-30  5:56   ` Jan Kiszka [this message]
2007-06-30 14:13     ` 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=4685F079.7090202@domain.hid \
    --to=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.