From: Philippe Gerum <rpm@xenomai.org>
To: Michael Haberler <mail17@mah.priv.at>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] q on rt_task_self() and mode switching
Date: Mon, 08 Jul 2013 15:37:45 +0200 [thread overview]
Message-ID: <51DAC0A9.1010709@xenomai.org> (raw)
In-Reply-To: <CE260BFE-CB8F-45DC-A46D-8CFE585069EC@mah.priv.at>
On 07/08/2013 03:23 PM, Michael Haberler wrote:
> if a userland RT thread gets modeswitched, the SIGXCPU handler obviously still executes in the RT domain,
Nope. All regular signal handlers are executed in the linux domain.
Xenomai 2.x does not provide real-time signal handlers fired from
primary mode.
at least rt_task_self() returns a valid task descriptor - fine.
>
> If a kernel RT thread misses the release point, it seems the thread is immediately switched to linux scheduling
With Xenomai 2.x, there is no migration to secondary mode for a
kernel(-only) RT thread.
- or at least rt_task_self() returns NULL in this scenario:
>
> int result = rt_task_wait_period(&overruns);
> switch (result) {
>
> case -ETIMEDOUT: // release point was missed
> task = rt_task_self(); // this returns NULL
>
>
> not a big thing - I just would like to get at the thread name for error message purposes; any way to do this?
>
Certainly, but which context does the code above run? On top of some
ioctl()?
> - Michael
>
>
>
>
>
> _______________________________________________
> Xenomai mailing list
> Xenomai@xenomai.org
> http://www.xenomai.org/mailman/listinfo/xenomai
>
--
Philippe.
next prev parent reply other threads:[~2013-07-08 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 13:23 [Xenomai] q on rt_task_self() and mode switching Michael Haberler
2013-07-08 13:37 ` Philippe Gerum [this message]
2013-07-08 13:45 ` Michael Haberler
2013-07-08 13:55 ` Philippe Gerum
2013-07-08 14:03 ` Michael Haberler
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=51DAC0A9.1010709@xenomai.org \
--to=rpm@xenomai.org \
--cc=mail17@mah.priv.at \
--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.