Philippe Gerum wrote: > Jan Kiszka wrote: >> Philippe Gerum wrote: >>> Jan Kiszka wrote: >>>> Meanwhile I played with some light-weight approach to relax a thread >>>> that received a signal (according to do_sigwake_event). Worked, but only >>>> once due to a limitation (if not bug) of I-pipe x86: in __ipipe_run_isr, >>>> it does not handle the case that a non-root handler may alter the >>>> current domain, causing corruptions to the IPIPE_SYNC_FLAG states of the >>>> involved domains. >>> It is not a bug, this is wanted. ISR must neither change the current >>> domain nor migrate CPU; allowing this would open Pandora's box. >> And if there is no way to migrate from within an ISR, we can bury any >> attempt to deliver signals to spinning Xenomai threads - or what other >> context would remain to Xenomai for triggering migration? >> > > The two-phase solution I have mentioned would work.
I think you can only handle lethal signals that way, not non-lethal like SIGSTOP. Jan
Description: OpenPGP digital signature
_______________________________________________ Xenomai-core mailing list Xenomaiemail@example.com https://mail.gna.org/listinfo/xenomai-core