From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH] optimise syscall mux-code calculation
Date: Sat, 15 Jul 2006 17:56:30 +0200 [thread overview]
Message-ID: <17593.4142.482000.586615@domain.hid> (raw)
In-Reply-To: <44B8D412.1080002@domain.hid>
Jan Kiszka wrote:
> Jan Kiszka wrote:
> > ...
> > Ok, I will rework this patch.
> >
>
> And here is -v2 (for post 2.2 trunk). It keeps the ABI but changes the
> API wrt __xeno_mux_code. As this change gets widely caught by
> xeno_user_skin_init, the modifications are limited.
>
> At this chance I also converted the rtdm library to the generic
> initialisation code. I tweaked nucleus/bind.h a bit so that one can
> control via XENO_DISABLE_MLOCKALL_DETECTION if the related code gets
> built into the lib. This appeared to be reasonable to me because librtdm
> doesn't create its own RT threads, thus the check should be better left
> to those skins who do so. Anyone any better idea, or is this acceptable?
> If a separate patch is preferred, I will break out this change.
Another reason why rtdm did not use the generic initialization code is
that RTDM did not call exit upon failure to bind, and let a later call
to open fail. I do not know if it was desirable, but it was a feature of
the previous implementation.
--
Gilles Chanteperdrix.
next prev parent reply other threads:[~2006-07-15 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 11:13 [Xenomai-core] [PATCH] optimise syscall mux-code calculation Jan Kiszka
2006-07-15 2:24 ` Philippe Gerum
2006-07-15 8:06 ` Jan Kiszka
2006-07-15 8:31 ` Philippe Gerum
2006-07-15 8:37 ` Jan Kiszka
2006-07-15 15:11 ` Philippe Gerum
2006-07-15 11:40 ` Jan Kiszka
2006-07-15 12:13 ` Gilles Chanteperdrix
2006-07-15 12:29 ` Jan Kiszka
2006-07-15 15:56 ` Gilles Chanteperdrix [this message]
2006-07-16 9:43 ` Jan Kiszka
2006-07-16 14:47 ` Jan Kiszka
2006-07-19 9:25 ` 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=17593.4142.482000.586615@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@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.