This series is intended to help user to set timer in frames that OS allows him. The timer resolution shouldn't be better than system allows, minimum timeout shouldn't be more than resolution, and warn application that CPU0, that is used for tick notification handling, can have impact on worker thread running on CPU0.
This patch series helps to close a bug: https://bugs.linaro.org/show_bug.cgi?id=1449 This series combines different patches and see previous versions: [lng-odp] [PATCH v3] linux-generic: odp_timer: warn if tick is lost https://lists.linaro.org/pipermail/lng-odp/2015-November/017150.html [lng-odp] [PATCH] linux-generic: cpumask: exclude CPU0 from odp_cpumask_default_worker https://lists.linaro.org/pipermail/lng-odp/2015-October/016542.html [lng-odp] [PATCH] example: timer: don't set timeout less than resolution https://lists.linaro.org/pipermail/lng-odp/2015-October/016772.html Ivan Khoronzhuk (3): example: timer: warn if timeout less than resolution linux-generic: odp_timer: warn if tick is late linux-generic: cpumask: warn that CPU0 is used by control and worker thread example/timer/odp_timer_test.c | 3 +++ platform/linux-generic/odp_cpumask_task.c | 4 ++++ platform/linux-generic/odp_timer.c | 6 ++++++ 3 files changed, 13 insertions(+) -- 1.9.1 _______________________________________________ lng-odp mailing list lng-odp@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lng-odp
