8dad54c914
Previously, the timer was used to remember the state of the time slices. This was sufficient before priorities entered the scene as a thread always received a fresh time slice when he was scheduled away. However, with priorities this isn't always the case. A thread can be preempted by another thread due to a higher priority. In this case the low-priority thread must remember how much time he has consumed from its current time slice because the timer gets re-programmed. Otherwise, if we have high-priority threads that block and unblock with high frequency, the head of the next lower priority would start with a fresh time slice all the time and is never superseded. fix #1287 |
||
|---|---|---|
| .. | ||
| etc | ||
| include | ||
| lib | ||
| mk | ||
| run | ||
| src | ||
| README | ||
This is generic part of the Genode implementation. It consists of two parts: :_Core_: is the ultimate root of the Genode application tree and provides abstractions for the lowest-level hardware resources such as RAM, ROM, CPU, and generic device access. All generic parts of Core can be found here - for system-specific implementations refer to the appropriate 'base-<system>' directory. :_Base libraries and protocols_: that are used by each Genode component to interact with other components. This is the glue that holds everything together.