Hi Gerwin, Hey look, I can participate in the TSC! I did consider this when building the api. There were two reasons against it: 1. a painful api (most user-apps want ticks) - but this could always be pushed into libsel4 where one has the advantage of an FPU/being able to use a divisor - specific users could also determine their own accuracy/precision trade offs 2. as Gernot mentioned in the thread, clock rate changes could be a concern - this was the deciding factor I believe as long as the kernel timer is independent of the CPU frequency due to scaling (which IIRC is the case for the arm generic timers which these days are thankfully the norm, unlike earlier hardware) changing to ticks shouldn't be an issue, and will remove a lot of painful logic in the kernel. Would be worth confirming this on supported hardware. Cheers Anna. On Tue, Sep 9, 2025 at 9:58 AM Kent Mcleod <kent.mcleod72@gmail.com> wrote:
I'm in favour of pushing the conversions out to userlevel. Also with the mainline kernel's millisecond representation of ticks used in scheduling and the domain scheduler static schedule.
Kent.
On Tue, Sep 9, 2025 at 7:39 AM Gerwin Klein <gerwin.klein@proofcraft.systems> wrote:
Any opinions on changing the MCS from time in us to time in timer ticks?
https://sel4.discourse.group/t/pre-rfc-change-mcs-api-from-us-to-ticks/1011
Cheers, Gerwin _______________________________________________ Tsc-members mailing list -- tsc-members@sel4.systems To unsubscribe send an email to tsc-members-leave@sel4.systems
_______________________________________________ Tsc-members mailing list -- tsc-members@sel4.systems To unsubscribe send an email to tsc-members-leave@sel4.systems