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: "Charlton, John" <john.charlton@domain.hid>,
	xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [pull request] Fixes and workarounds for the cond issues
Date: Thu, 04 Mar 2010 11:40:17 +0100	[thread overview]
Message-ID: <4B8F8E11.9060902@domain.hid> (raw)
In-Reply-To: <4B8D9711.5090704@domain.hid>

Jan Kiszka wrote:
> The following changes since commit af93ec87f975b387243127090b578d57922b38dc:
>   Gilles Chanteperdrix (1):
>         posix: fix recursive condvar implementation
> 
> are available in the git repository at:
> 
>   git://git.xenomai.org/xenomai-jki.git for-upstream
> 
> These patches pass basic testings, specifically our extended testsuite,
> but I'm still unhappy with the workaround. Specifically the fact that we
> lose -EINTR as valid return code for the Native side is fairly annoying.
> 
> For that reason, I will continue to work out fixed prologue/epilogue
> syscalls for both skins that up-to-date user space will be able to
> benefit from (native kernel space part is already done). The majority of
> users will continue to update kernel and user space synchronously
> anyway, for the rest we will provide these workarounds here.

Let us calm down, and avoid pushing changes which are worse than the
issue they try and correct. I will not publish anything on these issues
before this week-end. Instead of modifying the mutex-torture unt test, I
will try and write a condvar-torture unit test, which exhaustively test
all the return values of pthread_cond_wait/rt_cond_wait, including
interruption by signals during the cond_wait, and the epilogue.

-- 
					    Gilles.


  reply	other threads:[~2010-03-04 10:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 22:54 [Xenomai-core] [pull request] Fixes and workarounds for the cond issues Jan Kiszka
2010-03-04 10:40 ` Gilles Chanteperdrix [this message]
2010-03-04 10:30   ` [Xenomai-core] ADEOS patch for LPC3250 Pierre Ficheux
2010-03-04 13:37     ` Gilles Chanteperdrix
2010-03-04 11:26   ` [Xenomai-core] [pull request] Fixes and workarounds for the cond issues Jan Kiszka
2010-03-04 11:28     ` Jan Kiszka
2010-03-04 13:45     ` Gilles Chanteperdrix
2010-03-04 13:53       ` Jan Kiszka
     [not found] ` <CF7FB0793253794F9F45991443E5FE2006483DE99F@us194mx002.tycoelectronics.net>
2010-03-05 18:36   ` Gilles Chanteperdrix
2010-03-08 18:42     ` Charlton, John
2010-03-08 18:47       ` Gilles Chanteperdrix
2010-03-08 20:39         ` Charlton, John
2010-03-08 20:42           ` Gilles Chanteperdrix
2010-03-08 21:13             ` Charlton, John
2010-03-08 16:32   ` Gilles Chanteperdrix

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=4B8F8E11.9060902@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jan.kiszka@domain.hid \
    --cc=john.charlton@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.