2f35873885
The scheduler cannot correctly schedule once the timestamp exceeds MAX_RELEASE_TIME as releases beyond this point may be subject to overflow. For most systems this should still allow a great many years if the timestamp starts from 0 at system boot. Some systems currently start with a random initial timestamp and my begin with a timestamp that prvents correct budgeting. This assert helps to catch cases where scheduling becomes invalid due to the timestamp exceeding the give bound. Signed-off-by: Curtis Millar <curtis.millar@data61.csiro.au> |
||
|---|---|---|
| .. | ||
| boot.h | ||
| cspace.h | ||
| faulthandler.h | ||
| sporadic.h | ||
| stack.h | ||
| thread.h | ||
| traps.h | ||
| vspace.h | ||