summaryrefslogtreecommitdiff
path: root/include/drivers/system_timer.h
diff options
context:
space:
mode:
authorRamesh Thomas <ramesh.thomas@intel.com>2017-02-05 19:37:19 -0800
committerAnas Nashif <nashif@linux.intel.com>2017-04-27 13:46:28 +0000
commit89ffd44dfb5c6df7e12b902ef8b117fdaff0bcae (patch)
tree1412218453ccf0648c404cce80e83d18ef493f4a /include/drivers/system_timer.h
parent62eea121b357eae64fe00d996e2193d2b4638d1e (diff)
kernel: tickless: Add tickless kernel support
Adds event based scheduling logic to the kernel. Updates management of timeouts, timers, idling etc. based on time tracked at events rather than periodic ticks. Provides interfaces for timers to announce and get next timer expiry based on kernel scheduling decisions involving time slicing of threads, timeouts and idling. Uses wall time units instead of ticks in all scheduling activities. The implementation involves changes in the following areas 1. Management of time in wall units like ms/us instead of ticks The existing implementation already had an option to configure number of ticks in a second. The new implementation builds on top of that feature and provides option to set the size of the scheduling granurality to mili seconds or micro seconds. This allows most of the current implementation to be reused. Due to this re-use and co-existence with tick based kernel, the names of variables may contain the word "tick". However, in the tickless kernel implementation, it represents the currently configured time unit, which would be be mili seconds or micro seconds. The APIs that take time as a parameter are not impacted and they continue to pass time in mili seconds. 2. Timers would not be programmed in periodic mode generating ticks. Instead they would be programmed in one shot mode to generate events at the time the kernel scheduler needs to gain control for its scheduling activities like timers, timeouts, time slicing, idling etc. 3. The scheduler provides interfaces that the timer drivers use to announce elapsed time and get the next time the scheduler needs a timer event. It is possible that the scheduler may not need another timer event, in which case the system would wait for a non-timer event to wake it up if it is idling. 4. New APIs are defined to be implemented by timer drivers. Also they need to handler timer events differently. These changes have been done in the HPET timer driver. In future other timers that support tickles kernel should implement these APIs as well. These APIs are to re-program the timer, update and announce elapsed time. 5. Philosopher and timer_api applications have been enabled to test tickless kernel. Separate configuration files are created which define the necessary CONFIG flags. Run these apps using following command make pristine && make BOARD=qemu_x86 CONF_FILE=prj_tickless.conf qemu Jira: ZEP-339 ZEP-1946 ZEP-948 Change-Id: I7d950c31bf1ff929a9066fad42c2f0559a2e5983 Signed-off-by: Ramesh Thomas <ramesh.thomas@intel.com>
Diffstat (limited to 'include/drivers/system_timer.h')
-rw-r--r--include/drivers/system_timer.h10
1 files changed, 10 insertions, 0 deletions
diff --git a/include/drivers/system_timer.h b/include/drivers/system_timer.h
index dbaf3d4cd..bb48712dd 100644
--- a/include/drivers/system_timer.h
+++ b/include/drivers/system_timer.h
@@ -38,9 +38,19 @@ extern void sys_clock_disable(void);
#ifdef CONFIG_TICKLESS_IDLE
extern void _timer_idle_enter(s32_t ticks);
extern void _timer_idle_exit(void);
+#else
+#define _timer_idle_enter(ticks) do { } while ((0))
+#define _timer_idle_exit() do { } while ((0))
#endif /* CONFIG_TICKLESS_IDLE */
extern void _nano_sys_clock_tick_announce(s32_t ticks);
+#ifdef CONFIG_TICKLESS_KERNEL
+extern void _set_time(u32_t time);
+extern u32_t _get_program_time(void);
+extern u32_t _get_remaining_program_time(void);
+extern u32_t _get_elapsed_program_time(void);
+extern u64_t _get_elapsed_clock_time(void);
+#endif
extern int sys_clock_device_ctrl(struct device *device,
u32_t ctrl_command, void *context);