From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Smith <2michael.smith@gmail.com>, xenomai@xenomai.org
Subject: Re: [Xenomai] RTDM !xnpod_unblockable_p() question
Date: Wed, 13 Aug 2014 22:04:41 +0200 [thread overview]
Message-ID: <53EBC4D9.9040402@xenomai.org> (raw)
In-Reply-To: <CANWkrRN=ExZ4qgcXp8+d2NOzBHUvWb2u6Zu8twmr8Vo2VZnnqg@mail.gmail.com>
On 08/13/2014 02:28 PM, Michael Smith wrote:
> but there is just not enough information in the code
> or documentation for me to solve it.
Actually, the information can very well be found in the source code.
#define xnpod_unblockable_p() \
(xnpod_asynch_p() || xnthread_test_state(xnpod_current_thread(), XNROOT))
If you had digged a bit, you would have found that the failing test was
!xnthread_test_state(xnpod_current_thread(), XNROOT)
Which clearly means that you were calling rtdm_mutex_lock() from the
context of the root thread and that the root thread is unblockable.
Now, if you do not understand what the root thread is, or why it can
not be suspended from Xenomai's scheduler point of view, clearly, there
are a thing or two you have not taken the time to understand about
Xenomai. So, please do not reverse the roles: you are the one who has
not read enough documentation, please do not accuse us of not having
written enough.
--
Gilles.
next prev parent reply other threads:[~2014-08-13 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 12:28 [Xenomai] RTDM !xnpod_unblockable_p() question Michael Smith
2014-08-13 12:52 ` Philippe Gerum
2014-08-13 12:55 ` Philippe Gerum
2014-08-13 20:04 ` Gilles Chanteperdrix [this message]
[not found] ` <CANWkrROgE=AVv_Qq9hkvS+kJ+Wx1zepOjJQ2gAX7qwNYJqhYBw@mail.gmail.com>
2014-08-14 7:02 ` [Xenomai] Fwd: " Michael Smith
2014-08-14 7:20 ` 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=53EBC4D9.9040402@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=2michael.smith@gmail.com \
--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.