Nicolas Pitre b60cb9cc80 tests: kernel: timer_behavior: improve timer_tick_train output ...

Print the "perfect" reference period for easier evaluation.
Suggest a remedy to the missed ticks problem.

Still, that wasn't satisfactory. Implemented a count of missed ticks
to get to the bottom of this issue. Found that missed ticks always came
to a perfect count of 40.

Incidentally, the busy loop prints a line every 250 ms and the test spans
10 seconds. There are no such coincidences.

Turns out that CONFIG_PRINTK_SYNC was set by default. This disables IRQs
for the serial output duration, which can be quite long at 115200 bauds.
Given a 60-ish character line length, this represents more than 5 ms of
no IRQ servicing during a timer latency measurement test which is bad.
So make sure CONFIG_PRINTK_SYNC=n for proper statistics.

Signed-off-by: Nicolas Pitre <npitre@baylibre.com>

2023-02-19 20:34:37 -05:00

..

cycle64

includes: prefer <zephyr/kernel.h> over <zephyr/zephyr.h>

2022-09-05 16:31:47 +02:00

starve

tests: kernel: timer: starve: Adjust timeout value

2022-12-21 10:11:23 +01:00

timer_api

tests: kernel: do not set excluded as integration platform

2022-11-30 16:00:42 -05:00

timer_behavior

tests: kernel: timer_behavior: improve timer_tick_train output

2023-02-19 20:34:37 -05:00

timer_error_case

tests: use ignore_fault field instead of tags

2022-11-25 06:38:05 -05:00

timer_monotonic

yamllint: indentation: fix files in tests/

2023-01-04 14:23:53 +01:00