Difference between revisions of "Time namespace"

From CRIU
Jump to: navigation, search
(remove TODO, add LWN link)
 
Line 3: Line 3:
 
[https://github.com/checkpoint-restore/criu/pull/1002 The time namespace support] in CRIU has been merged in the [[Download/criu/3.14 | 3.14 release]].  
 
[https://github.com/checkpoint-restore/criu/pull/1002 The time namespace support] in CRIU has been merged in the [[Download/criu/3.14 | 3.14 release]].  
  
=TODO=
+
[https://lwn.net/Articles/766089/ LWN article about time namespaces]
==Maybe later==
 
 
 
* Make start-time remain "unchanged" after C/R
 
* arm64/arm32/s390/power64 - add archs vvar support (nit: big/little-endianess for timespec::nsec)
 
* REALTIME-related:
 
** REALTIME offsets
 
** vvar offsets will need synchronization (like gtod_read_begin()/gtod_read_retry())
 
** vfs modification/creation time should work
 
** starttime in /proc/pid/stat
 
** btime in /proc/stat
 
** utime()/utimes()/futimesat() (with times == NULL)
 
** utimensat()/futimens() - with UTIME_NOW
 
** mq_timedsend()/mq_timedreceive()
 
** semtimedop()
 
* 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
 
* What about other kinds of counters like perf events and trace events?
 
  
 
=Links=
 
=Links=

Latest revision as of 14:53, 29 April 2020