Re: [Xenomai-help] handling threads within a pod

[Jan Kiszka <jan.kiszka@domain.hid>]

Philippe Gerum wrote:
> ...
> Then use the XNHELD bit which has been specifically added as a
> suspensive condition to handle temporal partitioning. This way, XNSUSP
> remains available for suspending processes forcibly within a partition
> (suspension bits are conjunctive). IOW, only the processes pertaining to
> the running partition will have the XNHELD bit cleared, others will have
> this bit set, and as such, suspended by the nucleus, which is what you
> want.
> 
> void deactivate_partition (struct ima380_partition *pt)
> {
> 	foreach(thread in pt->procq) {
> 		xnpod_suspend_thread(thread,XNHELD,XN_INFINITE,NULL);
> 	}
> }
> 
> void activate_partition (struct ima380_partition *pt)
> {
> 	foreach(thread in pt->procq) {
> 		xnpod_resume_thread(thread,XNHELD);
> 	}
> }

I wonder if there isn't the risk of mixing up the schedule inside the
partitions by suspending/resuming this way. I think the order of
resuming those threads that were ready before must match the original
order in the ready-queue at suspension time.

> 
> The partition slicer can be implemented as a simple periodic timer,
> whose handler activates existing partitions in a round-robin fashion.
> 
> FWIW, mimicking arinc653 over the nucleus is a no-brainer, so there's
> good hope for IMA380.
> 

Jan