From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: Xenomai core <Xenomai-core@domain.hid>
Subject: Re: [Xenomai-core] [RFC] Fixes for domain migration races
Date: Wed, 27 Jul 2011 20:44:35 +0200 [thread overview]
Message-ID: <4E305C93.6010000@domain.hid> (raw)
In-Reply-To: <4E2527B2.3030305@domain.hid>
On 07/19/2011 08:44 AM, Jan Kiszka wrote:
> Hi,
>
> I've just uploaded my upstream queue that mostly deals with the various
> races I found in the domain migration code.
>
> One of my concerns raised earlier turned out to be for no reason: We do
> not allow Linux to wake up a task that has TASK_ATOMICSWITCH set. So the
> deletion race can indeed be fixed by the patch I sent earlier.
So, I still have the same question: is not the solution of synchronizing
with the gatekeeper as soon as we get out from schedule in secondary
mode better than waiting the task_exit callback? It looks more correct,
and it avoids gksched.
--
Gilles.
next prev parent reply other threads:[~2011-07-27 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 6:44 [Xenomai-core] [RFC] Fixes for domain migration races Jan Kiszka
2011-07-27 18:44 ` Gilles Chanteperdrix [this message]
2011-07-28 16:44 ` 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=4E305C93.6010000@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Xenomai-core@domain.hid \
--cc=jan.kiszka@domain.hid \
/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.