From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai@xenomai.org
Subject: Re: [Xenomai-core] Pending ownership and resource stealing
Date: Wed, 10 May 2006 19:34:07 +0200 [thread overview]
Message-ID: <17506.9231.555209.471522@domain.hid> (raw)
In-Reply-To: <44621B00.7090703@domain.hid>
Philippe Gerum wrote:
> This means that skins now _must_ fix their internal state when unblocked
> from xnsynch_sleep_on() if they happen to track their own resource owner
> field for instance, since they might become the owner of such resource
> without any unlock/release/whatever routine being called at the said
> skin level. I've fixed a couple of skins for that purpose (not checked
> RTDM btw), but it would be safer if you could double-check the impact of
> such change on the interfaces you've crafted.
When waking up, how do we know that we are in the problematic situation
? Can we do the house keeping in the callback registered with
xnsynch_register_cleanup, or are you talking of a different situation ?
--
Gilles Chanteperdrix.
next prev parent reply other threads:[~2006-05-10 17:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 7:58 [Xenomai-core] [bug] zombie mutex owners Jan Kiszka
2006-05-10 9:16 ` Dmitry Adamushko
2006-05-10 10:07 ` Jan Kiszka
2006-05-10 10:40 ` Philippe Gerum
2006-05-10 10:52 ` Philippe Gerum
2006-05-10 11:49 ` Jan Kiszka
2006-05-10 16:39 ` Philippe Gerum
2006-05-10 12:28 ` Philippe Gerum
2006-05-10 16:55 ` [Xenomai-core] Pending ownership and resource stealing Philippe Gerum
2006-05-10 17:34 ` Gilles Chanteperdrix [this message]
2006-05-10 18:39 ` Philippe Gerum
2006-05-10 20:00 ` Gilles Chanteperdrix
2006-05-10 21:25 ` Philippe Gerum
2006-05-11 17:17 ` Gilles Chanteperdrix
2006-05-11 22:39 ` Philippe Gerum
2006-05-10 17:34 ` Jan Kiszka
2006-05-10 21:23 ` Philippe Gerum
2006-05-11 7:56 ` Jan Kiszka
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=17506.9231.555209.471522@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=rpm@xenomai.org \
--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.