On 1/8/2022 5:22 pm, Sebastian Huber wrote: > A relative CLOCK_REALTIME time out shall not be affected by CLOCK_REALTIME > changes through clock_settime(). Since our CLOCK_REALTIME is basically just > CLOCK_MONOTONIC plus an offset, we can simply use the CLOCK_MONOTONIC watchdog > for relative CLOCK_REALTIME time outs.
Thank for this. I can confirm it works with the modified test code I attached to the ticket. I am ts-validation-no-clock-0.exe now failing on xilinx_zynq_a9_qemu but I am not sure? There is one issue my test changes have exposed and that is the ticks a thread sleeps for is 1 more than the requested number. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
