iscussion on the delayed start of major frame with
> ARINC653 scheduler
>
> On 7/14/25 11:11, Weber, Matthew wrote:
> >
> > > As a heads up, since this is a bit of a bigger change then some of
> > > the recent
> > patches, I am working on running a st
On 7/14/25 11:11, Weber, Matthew wrote:
>
> > As a heads up, since this is a bit of a bigger change then some of the
> > recent
> patches, I am working on running a stress test on it, which may take some
> time.
>
> Out of curiosity, is that something we could plan to run on our end as well
>
RNAL] RE: Discussion on the delayed start of major frame with
> ARINC653 scheduler
>
> EXT email: be mindful of links/attachments.
>
> As a heads up, since this is a bit of a bigger change then some of the recent
> patches, I am working on running a stress test on it, which may
On 7/10/25 2:36, Choi, Anderson wrote:
> What would be the next step? Will you submit the patch or should I revise the
> patch I have already submitted with the change you suggested?
I do not have a preference, but since you already have a patch thread started,
it is probably easiest to just hav
Nathan,
> I'm not sure this will work if the first minor frame is also missed (which can
> happen in some odd cases). In that scenario, you need to iterate through the
> schedule after resyncing the expected next major frame.
>
> Building off your changes, this should work:
>
> -if ( sched_
+Jeff
On 6/25/25 23:51, Choi, Anderson wrote:
> We are observing a slight delay in the start of major frame with the current
> implementation of ARINC653 scheduler, which breaks the determinism in the
> periodic execution of domains.
>
> This seems to result from the logic where the variable "nex
Stewart,
> On 6/25/25 23:50, Choi, Anderson wrote:
>> We are observing a slight delay in the start of major frame with the current
> implementation of ARINC653 scheduler, which breaks the determinism in the
> periodic execution of domains.
>>
>> This seems to result from the logic where the varia
On 6/25/25 23:50, Choi, Anderson wrote:
> We are observing a slight delay in the start of major frame with the current
> implementation of ARINC653 scheduler, which breaks the determinism in the
> periodic execution of domains.
>
> This seems to result from the logic where the variable "next_maj
We are observing a slight delay in the start of major frame with the current
implementation of ARINC653 scheduler, which breaks the determinism in the
periodic execution of domains.
This seems to result from the logic where the variable "next_major_frame" is
calculated based on the current time
