All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Pending patches
Date: Thu, 15 Jan 2009 11:00:21 +0000	[thread overview]
Message-ID: <496F1745.2000401@domain.hid> (raw)
In-Reply-To: <496F1041.20306@domain.hid>

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Hi,
>>
>> currently I have the following six patches in my assorted queue
>> (git://git.kiszka.org/xenomai.git queue/assorted). All have been posted
>> before, I just rebased them since then a few times. Should I repost
>> any/all of them (would be no problem), or are some already queued for
>> potential merge?
>>
>> Jan
>>
>> (...)
>> commit a631ab2c531d5e381ba8a0a59bf301a0276d9f99
>> Author: Jan Kiszka <jan.kiszka@domain.hid>
>> Date:   Thu Jan 15 11:10:24 2009 +0100
>>
>>     POSIX: Do not auto-shadow main with dlopen enabled
>>     
>>     Don't perform auto-shadowing in POSIX skin if we might be loaded via
>>     dlopen. Otherwise the wrong thread, the undefined dlopen caller, may be
>>     (re-)shadowed, assigning wrong scheduling settings.
>>     
>>     Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>
>>
>>  src/skins/posix/init.c |   43 ++++++++++++++++++++++++++++---------------
>>  1 files changed, 28 insertions(+), 15 deletions(-)
>>
>> commit 91ae3da822ca558804bf33be4d164ea4c2667c1b
>> Author: Jan Kiszka <jan.kiszka@domain.hid>
>> Date:   Thu Jan 15 11:10:24 2009 +0100
>>
>>     Replace --without-__tread with --enable-dlopen-skins
>>     
>>     In practice, you only want to disable __thread support when Xenomai skin
>>     libraries should be loadable via dlopen. Therefore rename the related
>>     configure switch accordingly.
>>     
>>     Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>
>>
> 
> Nack these two ones: one of the gcc bugs I have found on ARM is related
> to __thread (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38815). So,
> even though I have found a work around for the bug, I am not sure that
> it works all the time, so disabling __thread on ARM is safer. Especially
> since __thread does not bring any performance improvement over
> pthread_(get|set)specific on ARM.

Actually, I am not opposed to the first, only to the second.

-- 
                                                 Gilles.


  reply	other threads:[~2009-01-15 11:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 10:19 [Xenomai-core] Pending patches Jan Kiszka
2009-01-15 10:30 ` Gilles Chanteperdrix
2009-01-15 11:00   ` Gilles Chanteperdrix [this message]
2009-01-15 11:31     ` Jan Kiszka
2009-01-15 13:02       ` Gilles Chanteperdrix
2009-01-15 14:12         ` Jan Kiszka
2009-01-15 11:28   ` Jan Kiszka
2009-01-15 13:09     ` Gilles Chanteperdrix
2009-01-15 14:17       ` Jan Kiszka
2009-01-15 21:46         ` Jan Kiszka
2009-01-15 10:49 ` Philippe Gerum
2009-01-15 11:24   ` Jan Kiszka
2009-01-15 12:09     ` Philippe Gerum
2009-01-15 13:55       ` Jan Kiszka
2009-01-15 14:16         ` Philippe Gerum
2009-01-19 23:18           ` Philippe Gerum
2009-01-19 23:35             ` Jan Kiszka
2009-01-20  8:49               ` Philippe Gerum
2009-01-20  9:06                 ` Jan Kiszka
2009-01-20  9:18                   ` Jan Kiszka
2009-01-20  9:22                   ` Philippe Gerum
2009-01-27 13:10                 ` Jan Kiszka
2009-01-27 13:26                   ` Jan Kiszka
2009-01-27 13:28                     ` Gilles Chanteperdrix
2009-01-27 13:29                   ` Philippe Gerum
2009-01-27 13:40                     ` Gilles Chanteperdrix
2009-01-27 13:40                   ` 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=496F1745.2000401@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.