Re: [PATCH 2/5] Make RTDM tasks behave, part I

[Richard Weinberger <richard@sigma-star.at>]

On Mittwoch, 28. Jänner 2026 14:23 Philippe Gerum wrote:
> > +	while (!rtdm_task_should_stop()) {
> >  		ret = rtdm_event_wait(&k_tuner->barrier);
> > -		if (ret)
> > +		if (ret == -EINTR)
> > +			continue;
> 
> Using -EINTR is going to be a problem if xnthread_unblock() is called to
> forcibly wake up a kernel task from a sleep. In this case, you would not
> be able to distinguish a signal receipt from a forcible
> unblock. -ERESTARTSYS may be better for that specific purpose in the
> RTDM API.

What is the expected behavior of a RTDM task when xnthread_unblock() is called?
Currently, it will just terminate, which seems also odd to me.

With my changes it will at least revisit rtdm_task_should_stop() and distinguishing
between unblocking and signals is possible.
rtdm_task_should_stop() uses signal_pending().

Thanks,
//richard

-- 
​​​​​sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT UID/VAT Nr:
ATU 66964118 | FN: 374287y