From: Jan Kiszka <jan.kiszka@domain.hid>
To: "Brian L." <bluczkie@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] General question on Native Skin tasks
Date: Mon, 17 Apr 2006 15:33:32 +0200 [thread overview]
Message-ID: <4443992C.5000808@domain.hid> (raw)
In-Reply-To: <6ee4c8380604161110y3c937a74t9186bad2d9af2058@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
Brian L. wrote:
> If I create a native-skin RT_TASK from userspace with no flags, i.e.
>
> void task(void*)
> {
> for (;;) ;
> }
> int main()
> {
> RT_TASK t;
> rt_task_create(&t, 0, 3, 0);
> rt_task_start(&t,task,0);
> (do something which blocks)
> }
mlockall left out for simplicity? Or is it also missing on your real
test? In the latter case, occasional application crashes are "normal"
(as described below).
Philippe, you suggested some code for detecting this. We should really,
really add this soon (maybe to the exception path)!
>
> Should that task starve all other tasks? In what ways is it different
> behaviorally from an ordinary posix thread? I ask because I have a
> thread that might be spinning and a frozen system (back in the rtlinux
> days, spinning in the real-time domain was a surefire way to freeze
> without any other sign of trouble). If it is the case that this task
> outweighs an ordinary linux thread/task, how can I make it the same?
A task that has high priority than other system tasks has to outweigh
them. This has nothing to to with POSIX (standard Linux included!),
RTLinux, Xenomai, or whatever. But Xenomai has a simple watchdog to
recover from run-away RT threads.
>
> Also, I haven't completely tracked this down yet, but xenomai seems
> to be page-faulting in a loop and exploding rather spectacularly in a
> native-skin multithreaded program that doesn't do anything outside of
> relatively ordinary queue/mutex/task stuff. I'm upgrading to trunk to
> see if it goes away.
>
> Short of a serial cable, is there a way to capture Oops/Panic text as
> it flies by?
linux/Documentation/networking/netconsole.txt is another option.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-04-17 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-16 18:10 [Xenomai-help] General question on Native Skin tasks Brian L.
2006-04-17 13:33 ` Jan Kiszka [this message]
2006-04-17 14:50 ` Philippe Gerum
2006-04-17 17:35 ` Philippe Gerum
2006-04-17 20:03 ` Jan Kiszka
2006-04-17 20:44 ` Jan Kiszka
2006-04-18 19:53 ` Brian L.
2006-04-18 21:04 ` Jan Kiszka
2006-04-19 15:27 ` Brian L.
2006-04-19 17:18 ` Jan Kiszka
2006-04-19 17:42 ` Brian L.
2006-04-19 19:45 ` Jan Kiszka
2006-04-20 3:09 ` Li Yi
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=4443992C.5000808@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=bluczkie@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.