From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Henri Roosen <henriroosen@domain.hid>
Cc: Jan Kiszka <jan.kiszka@domain.hid>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Force switch back to primary domain
Date: Fri, 12 Feb 2010 18:16:09 +0100 [thread overview]
Message-ID: <4B758CD9.8060008@domain.hid> (raw)
In-Reply-To: <4B757B8D.9060307@domain.hid>
Gilles Chanteperdrix wrote:
> Henri Roosen wrote:
>> Ok, found some time to investigate the mutex problem we see on 2.5.1.
>>
>> I managed to reproduce with a basic app that uses the same way of
>> thread creation as we have in our app.
>> Please find attached the basic app. Note, it runs fine on Xenomai
>> 2.4.10. Fails on 2.5.1.
>>
>> Also, the problem does not show when creating the threads with rt_task_create.
>>
>> So the main question is, should it be possible to create threads with
>> the clone() system call and then shadowing the threads into the
>> Xenomai domain with rt_task_shadow()? And are we just lucky it runs
>> this way in 2.4.10?
>
> I would tend to think that Xenomai relies on the existence of a
> "pthread_t" associated with each thread, this only happens if the thread
> is created with pthread_create, not if created with clone.
>
> In fact, I even wonder how it works with 2.4.10.
> (rt_task_delete probably does not work in fact).
I think the problem comes from xeno_get_current_mode() or
xeno_get_current(). They use pthread services for sure if xenomai
user-space is not using __thread. Now, if using __thread, I do not know
for sure whether it should be working.
--
Gilles.
next prev parent reply other threads:[~2010-02-12 17:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 10:57 [Xenomai-help] Force switch back to primary domain Tschaeche IT-Services
2010-02-04 14:30 ` Gilles Chanteperdrix
2010-02-05 10:37 ` Tschaeche IT-Services
2010-02-05 11:19 ` Gilles Chanteperdrix
2010-02-05 11:50 ` Tschaeche IT-Services
2010-02-05 12:39 ` Henri Roosen
2010-02-05 13:34 ` Gilles Chanteperdrix
2010-02-05 14:38 ` Jan Kiszka
2010-02-05 15:27 ` Henri Roosen
2010-02-08 14:03 ` Gilles Chanteperdrix
2010-02-08 14:33 ` Henri Roosen
2010-02-09 10:06 ` Gilles Chanteperdrix
2010-02-09 10:09 ` Jan Kiszka
2010-02-09 10:14 ` Henri Roosen
2010-02-12 15:57 ` Henri Roosen
2010-02-12 16:02 ` Gilles Chanteperdrix
2010-02-12 17:16 ` Gilles Chanteperdrix [this message]
2010-02-12 17:20 ` Gilles Chanteperdrix
2010-02-15 9:07 ` Henri Roosen
2010-02-15 9:35 ` Jan Kiszka
2010-02-15 9:36 ` Philippe Gerum
2010-02-15 10:33 ` Henri Roosen
2010-02-15 10:47 ` 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=4B758CD9.8060008@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=henriroosen@domain.hid \
--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.