ostest/hrtimer: sync hrtimer ostest with latest hritmer update

[wangchdo]

Summary

sync hrtimer ostest with latest hritmer update

Impact

sync hrtimer ostest implementation, this change is isolated in hrtimer module

Testing

depends on apache/nuttx#18174

ostest passed on rv-virt:smp64 with hrtimer enabled

NuttShell (NSH)
nsh> 
nsh> uname -a
NuttX 0.0.0 d819e61456-dirty Jan 27 2026 11:19:53 risc-v rv-virt
nsh> 
nsh> ostest

(...)

user_main: smp call test
smp_call_test: Test start
smp_call_test: Call cpu 0, nowait
smp_call_test: Call cpu 0, wait
smp_call_test: Call cpu 1, nowait
smp_call_test: Call cpu 1, wait
smp_call_test: Call cpu 2, nowait
smp_call_test: Call cpu 2, wait
smp_call_test: Call cpu 3, nowait
smp_call_test: Call cpu 3, wait
smp_call_test: Call cpu 4, nowait
smp_call_test: Call cpu 4, wait
smp_call_test: Call cpu 5, nowait
smp_call_test: Call cpu 5, wait
smp_call_test: Call cpu 6, nowait
smp_call_test: Call cpu 6, wait
smp_call_test: Call cpu 7, nowait
smp_call_test: Call cpu 7, wait
smp_call_test: Call multi cpu, nowait
smp_call_test: Call in interrupt, wait
smp_call_test: Call multi cpu, wait
smp_call_test: Test success

user_main: hrtimer test

End of test memory usage:
VARIABLE  BEFORE   AFTER
======== ======== ========
arena     1fc11e0  1fc11e0
ordblks         6       11
mxordblk  1f77500  1f77500
uordblks     dd58    1dbf8
fordblks  1fb3488  1fa35e8

Final memory usage:
VARIABLE  BEFORE   AFTER
======== ======== ========
arena     1fc11e0  1fc11e0
ordblks         1       11
mxordblk  1fb60d0  1f77500
uordblks     b110    1dbf8
fordblks  1fb60d0  1fa35e8
user_main: Exiting
ostest_main: Exiting with status 0

[wangchdo]

Without this PR, ostest fails when hrtimer is enabled. Could you let me know which board configuration is used for ostest in the CI so I can enable hrtimer there and avoid repeated changes causing this regression? @xiaoxiang781216 @acassis @GUIDINGLI

It looks like my previous PR for enabling hritmer in CI pipeline only enabled the build check for it.......

[xiaoxiang781216]

Without this PR, ostest fails when hrtimer is enabled. Could you let me know which board configuration is used for ostest in the CI so I can enable hrtimer there and avoid repeated changes causing this regression? @xiaoxiang781216 @acassis @GUIDINGLI

It looks like my previous PR for enabling hritmer in CI pipeline only enabled the build check for it.......

here is the list:

./boards/risc-v/qemu-rv/rv-virt/configs/citest
./boards/sim/sim/sim/configs/citest
./boards/arm64/qemu/qemu-armv8a/configs/citest
./boards/arm64/fvp-v8r/fvp-armv8r/configs/citest
./boards/arm/imx6/sabre-6quad/configs/citest

[wangchdo]

Without this PR, ostest fails when hrtimer is enabled. Could you let me know which board configuration is used for ostest in the CI so I can enable hrtimer there and avoid repeated changes causing this regression? @xiaoxiang781216 @acassis @GUIDINGLI
It looks like my previous PR for enabling hritmer in CI pipeline only enabled the build check for it.......

here is the list:

./boards/risc-v/qemu-rv/rv-virt/configs/citest
./boards/sim/sim/sim/configs/citest
./boards/arm64/qemu/qemu-armv8a/configs/citest
./boards/arm64/fvp-v8r/fvp-armv8r/configs/citest
./boards/arm/imx6/sabre-6quad/configs/citest

I will enable hrtimer in citest when apache/nuttx#18174 and this PR #3380 got merged