All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Pending patches
Date: Thu, 15 Jan 2009 11:19:42 +0100	[thread overview]
Message-ID: <496F0DBE.5010108@domain.hid> (raw)

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 728fc8970e2032b3280971788f1223f3ad82d80d
Author: Jan Kiszka <jan.kiszka@domain.hid>
Date:   Thu Jan 15 11:10:24 2009 +0100

    xnpipe: Fix racy callback handlers
    
    Invocation of input, output and alloc handler must take place under
    nklock to properly synchronize with xnpipe_disconnect. Change all
    callers to comply with this policy.
    
    Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>

 ksrc/nucleus/pipe.c |   96 ++++++++++++++++++++++----------------------------
 1 files changed, 42 insertions(+), 54 deletions(-)

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>

 configure.in |   19 +++++++++++++------
 1 files changed, 13 insertions(+), 6 deletions(-)

commit 2af3cfcbcb21591089ed33da9e6efb0b5f78a71b
Author: Jan Kiszka <jan.kiszka@domain.hid>
Date:   Thu Jan 15 11:10:24 2009 +0100

    Mark libs nodlopen on initial-exec TLS
    
    Mark libs with nodlopen if initial-exec __thread variables are used
    because dlopen and this TLS model are in conflict.
    
    Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>

 configure.in                  |    3 +++
 src/skins/native/Makefile.am  |    2 +-
 src/skins/posix/Makefile.am   |    2 +-
 src/skins/psos+/Makefile.am   |    2 +-
 src/skins/rtai/Makefile.am    |    2 +-
 src/skins/rtdm/Makefile.am    |    2 +-
 src/skins/uitron/Makefile.am  |    2 +-
 src/skins/vrtx/Makefile.am    |    2 +-
 src/skins/vxworks/Makefile.am |    2 +-
 9 files changed, 11 insertions(+), 8 deletions(-)

commit 028d4766a38b6937d9a2c02a20022e3ee5b67b55
Author: Jan Kiszka <jan.kiszka@domain.hid>
Date:   Thu Jan 15 11:10:24 2009 +0100

    POSIX: Fix initialization of SCHED_RR threads
    
    Passing SCHED_RR as policy to pthread_create has currently not the
    desired effect. The kernel part expects that user space adjusts the
    policy and prio via __pse51_thread_setschedparam after setting up the
    shadow. And this is what the patch does by calling the wrapped
    pthread_setschedparam instead of the real one.
    
    Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>

 src/skins/posix/thread.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

commit 71666ce04ef216d281fe86ee82a5560c2b57c6dd
Author: Jan Kiszka <jan.kiszka@domain.hid>
Date:   Thu Jan 15 11:10:24 2009 +0100

    Handle priority changes of SCHED_RR tasks
    
    If shadowed Linux tasks with SCHED_RR policy change their priority,
    do_setsched_event currenty ignores this. Extend the condition to catch
    this case as well.
    
    Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>

 ksrc/nucleus/shadow.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

-- 
Siemens AG, Corporate Technology, CT SE 26
Corporate Competence Center Embedded Linux


             reply	other threads:[~2009-01-15 10:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 10:19 Jan Kiszka [this message]
2009-01-15 10:30 ` [Xenomai-core] Pending patches Gilles Chanteperdrix
2009-01-15 11:00   ` Gilles Chanteperdrix
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=496F0DBE.5010108@domain.hid \
    --to=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.