On Wed, 2025-07-09 at 09:08 +0900, Anderson Choi wrote: > ARINC653 specificaion requires partition scheduling to be > deterministic > and periodic over time. > > However, the use of current timestamp (now) as the baseline to > calculate > next_major_frame and next_switch_time introduces a delay in the start > of > major frame at every period, which breaks determinism and periodicity > in > partition scheduling. > > [...] > > Enforce the periodic behavior of partition scheduling by using the > value > next_major_frame as the base to calculate the start of major frame > and > the next domain switch time. In addition, push next_switch_time until > it's behind the current time to ensure positive runtime for the newly > selected domain to run. > This looks fine and correct to me, and it does indeed make perfect sense according to my knowledge of periodic real-time scheduling.
I think the patch can have my: Acked-by: Dario Faggioli <dfaggi...@suse.com> With the only caveat that I don't have any specific knowledge or experience with the details of the ARINC653 algorithms, and hence I cannot tell for sure whether or not the new behavior is also more adherent to the standard (although, I suspect it does) or not. If we want/need this kind of guarantee too, I hope that Stewart and/or Nathan can help... Regards, -- Dario Faggioli, Ph.D http://about.me/dario.faggioli Virtualization Software Engineer SUSE Labs, SUSE https://www.suse.com/ ------------------------------------------------------------------- <<This happens because _I_ choose it to happen!>> (Raistlin Majere)
signature.asc
Description: This is a digitally signed message part
