All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Michael Haberler <mail17@mah.priv.at>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Default options in the debian package
Date: Sat, 20 Apr 2013 10:19:14 +0200	[thread overview]
Message-ID: <51724F82.2000809@web.de> (raw)
In-Reply-To: <12ABCC03-FADF-4C5A-9CAE-CD9E5CA63A19@mah.priv.at>

On 2013-04-20 08:04, Michael Haberler wrote:
> 
> Am 19.04.2013 um 21:06 schrieb Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>:
> 
>> On 04/19/2013 01:46 PM, Leopold Palomo-Avellaneda wrote:
>>
>>> [1] 
>>> http://lists.mech.kuleuven.be/pipermail/orocos-users/2013-April/006986.html
>>
>>
>> Hi,
>>
>> that link does not tell us why you need this option. And that would be
>> the most important information.
> 
> with the linuxcnc package build I need to turn on --enable-dlopen-skins as well to get Python modules to work properly

OK, it looks like we should try harder to detect dlopen scenarios during
runtime to avoid build-time switches. This is likely Xenomai 3 material:

 - We need to disable TLS optimizations by default (no big deal).

 - In the POSIX skin constructor, we need to read out the mlockall
   state, lock everything if necessary, and restore the state
   accordingly afterward. The Nucleus may help us here if there is no
   adequate libc service (ABI change -> Xenomai 3).

 - IIRC, the problem with unconditional auto-shadowing back then were
   the improper scheduling parameters that POSIX used to apply. That
   was fixed a while back. So if we simple re-apply the current
   parameters, it should cause no harm in a dlopen scenario. But I need
   to check this again at work against our scenario.

Jan


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20130420/d3c1b2e3/attachment.pgp>

  reply	other threads:[~2013-04-20  8:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 11:46 [Xenomai] Default options in the debian package Leopold Palomo-Avellaneda
2013-04-19 12:48 ` Jan Kiszka
2013-04-19 19:06 ` Gilles Chanteperdrix
2013-04-20  6:04   ` Michael Haberler
2013-04-20  8:19     ` Jan Kiszka [this message]
2013-04-20 15:14       ` Gilles Chanteperdrix
2013-04-20 15:18         ` Jan Kiszka
2013-04-20 15:21           ` Gilles Chanteperdrix
2013-04-20 15:27             ` Jan Kiszka
2013-04-20 15:30               ` Gilles Chanteperdrix
2013-04-22  7:11                 ` Jan Kiszka
2013-04-22 11:37                   ` Gilles Chanteperdrix
2013-04-22 13:42                     ` Jan Kiszka
2013-04-22 18:57                       ` Gilles Chanteperdrix
2013-04-23  8:21                         ` Jan Kiszka
2013-04-23 11:20                           ` Gilles Chanteperdrix
2013-04-23 12:22                             ` Jan Kiszka
2013-04-23 12:40                             ` Philippe Gerum
2013-04-23 12:55                               ` Jan Kiszka
2013-04-23 13:03                                 ` Philippe Gerum
2013-04-22 15:15     ` Jeff Webb
2013-04-22  7:18   ` Leopold Palomo-Avellaneda
2013-04-22 11:42     ` Gilles Chanteperdrix
2013-04-22 14:54       ` Leopold Palomo-Avellaneda

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=51724F82.2000809@web.de \
    --to=jan.kiszka@web.de \
    --cc=mail17@mah.priv.at \
    --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.