Difference between revisions of "Time namespace"
Jump to navigation
Jump to search
| Line 26: | Line 26: | ||
* /proc/stat ticks? (top uses them e.g.) | * /proc/stat ticks? (top uses them e.g.) | ||
* pid creation time (probably different unrelated API) | * pid creation time (probably different unrelated API) | ||
| + | * clock_tai - if we care about isolation from host's time | ||
=Git= | =Git= | ||
Revision as of 01:01, 13 August 2018
Two things (for now) we want to solve with this:
- Shift timer's offsets
- Make start-time remain "unchanged" after C/R
- Continuous flow of monotonic time (CLOCK_MONOTONIC).
What about other kinds of counters like perf events and trace events?
TODO
Required in RFC
- timerfd
- timer_create()
- REALTIME offsets
- COARSE times
- RAW time
- vfs modification/creation time should work
- utime()/utimes()/futimesat() (with times == NULL)
- utimensat()/futimens() - with UTIME_NOW
- clock_nanosleep()
- mq_timedsend()/mq_timedreceive()
- semtimedop()
Maybe later
- arm64/arm32/s390/power64 - add archs vvar support
- Adjtime (too complicated for PoC)
- Cpu time for thread/pid/pgid (times())
- /proc/stat ticks? (top uses them e.g.)
- pid creation time (probably different unrelated API)
- clock_tai - if we care about isolation from host's time