From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Watchdog / immediate Linux signal delivery
Date: Sun, 08 Mar 2009 15:55:31 +0100 [thread overview]
Message-ID: <49B3DC63.4000209@domain.hid> (raw)
In-Reply-To: <49B3D98C.2070805@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> Jan Kiszka wrote:
>>>> Linux (e.g. via xnpod_suspend_thread(<cpu-hog>). Unfortunately, there is
>>>> no way to force a shadow thread into secondary mode to handle pending
>>>> Linux signals unless that thread issues a syscall once in a while. And
>>>> that raises the question if we shouldn't improve this as well while we
>>>> are on it.
>>>>
>>>> Granted, non-broken Xenomai user space threads always issue frequent
>>>> syscalls, otherwise the system would starve (and the watchdog would come
>>>> around). On the other hand, delaying signals till syscall prologues is
>>>> different from plain Linux behaviour...
>>>>
>>>> Comments, ideas?
>>> We discussed the issue of having a way to force threads to relax with
>>> Philippe, and we both had patches to make this work. However, the issue
>>> we recently had with the emulated iret on x86 makes me think that we can
>>> not relax at any point in time, the code surrounding the relax has to be
>>> made to allow a relax to occur.
>>>
>> Those issues were fixed. If we have similar problems around
>> __ipipe_handle_irq (I would expect the relaxation to take place in
>> xnintr_*_handler), then they should be fixed as well.
>>
>> The problem is that I currently do not see any other way of cleanly
>> terminating or debugging some Xenomai user space thread doing "while
>> (1);" (or any more complicated variation).
>
> I am not really opposed to the "force relax upon signal", thing, but the
> current approach used to work, at least with v2.3.x, so it must be my
> recent rework of thread termination which broke things, maybe we can
> repair them?
That was my first impression as well, but I've some feeling that it was
only silently broken so far. IIRC, Xenomai shadow threads must not run
in unmapped state after deleting their nucleus counterpart (but that's
what we do when the watchdog fired!). Rather, proper termination for
shadow threads goes via relaxing and then do_exit.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-03-08 14:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 10:42 [Xenomai-core] Watchdog / immediate Linux signal delivery Jan Kiszka
2009-03-08 13:41 ` Gilles Chanteperdrix
2009-03-08 14:23 ` Jan Kiszka
2009-03-08 14:43 ` Gilles Chanteperdrix
2009-03-08 14:55 ` Jan Kiszka [this message]
2009-03-09 15:50 ` Philippe Gerum
2009-03-09 16:44 ` Jan Kiszka
2009-03-09 17:02 ` Gilles Chanteperdrix
2009-03-09 17:15 ` Jan Kiszka
2009-03-09 17:27 ` Philippe Gerum
2009-03-09 17:09 ` Philippe Gerum
2009-03-09 17:12 ` Jan Kiszka
2009-03-09 17:37 ` Philippe Gerum
2009-03-09 23:49 ` Jan Kiszka
2009-03-10 9:20 ` Philippe Gerum
2009-03-09 17:27 ` Jan Kiszka
2009-03-09 17:38 ` Philippe Gerum
2009-03-09 17:58 ` Gilles Chanteperdrix
2009-03-10 11:09 ` Jan Kiszka
2009-03-10 13:17 ` Gilles Chanteperdrix
2009-03-09 23:46 ` 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=49B3DC63.4000209@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--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.