From: Kent Borg <kentborg@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Signals
Date: Wed, 25 Jan 2006 16:24:03 -0500 [thread overview]
Message-ID: <20060125162403.Y17353@domain.hid> (raw)
In-Reply-To: <43D7DD8C.60306@domain.hid>; from jan.kiszka@domain.hid on Wed, Jan 25, 2006 at 09:20:28PM +0100
On Wed, Jan 25, 2006 at 09:20:28PM +0100, Jan Kiszka wrote:
> > rt_task_catch() and rt_task_notify()?
>
> Those function are - in contrast to what to doc states - not yet
> available in userspace.
No wonder information on them is so sparse.
> So far Xenomai is lacking the infrastructure to
> deliver hard-RT signals to userspace threads, only the Linux signals are
> passed as usual.
But they are passed, that is good.
> Signals in multithreaded applications are tricky in general, even
> without Xenomai. You may try to play with pthread_kill and
> pthread_sigmask to control which thread receives a specific signal.
I have a very simple architecture, one thread is launched by regular
means, is launches the RT thread. It is the parent thread that
registers for the signal and (I think!) it is the one that gets the
interrupt.
> When the signal receiver is a Xenomai thread, the usual things happen:
> blocking on RT-resources is cleared, the thread is migrated to secondary
> mode, and the signal handler is invoked as one expects.
Very interesting. It sounds like Xenomai is doing cleanup I was
trying to do by hand. Maybe that is why I crapped the kernel, I am
cleaning up stuff that doesn't exist anymore. Should I deallocate my
RT fifos?
Thanks,
-kb
next prev parent reply other threads:[~2006-01-25 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 21:24 [Xenomai-help] Signals Kent Borg
2006-01-25 20:20 ` Jan Kiszka
2006-01-25 21:24 ` Kent Borg [this message]
2006-01-25 22:31 ` 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=20060125162403.Y17353@domain.hid \
--to=kentborg@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.