As time-namespaces are a new and mainstreamed version of ve-time, it's time to switch to it.
Notes: 1) ve-time does not need configuration on start, though time namespace needs configuration (offset == -now). 2) ve-time saved container start time but time namespaces save offset between host start time and container start time (offset == ve_start_time - now). 3) criu already knows how to handle time namespaces, though we need to do a compatibility layer to convert our ve.clock_* to offsets in time namespace for pre-vz9 to vz9 migration. 4) vdso time is already handled by time namespaces, though time namespace only virtualizes vvar page, so it should not intersect with our vdso virtualization for ve.os_release. https://jira.sw.ru/browse/PSBM-134393 Cyrill Gorcunov (1): ve: Add interface for ve::clock_[monotonic|bootbased] adjustment Kirill Tkhai (2): ve/time: Use ve_relative_clock in times() syscall and /proc/[pid]/stat ve: Virtualize sysinfo Pavel Tikhomirov (1): ve/time: remove our per-ve times in favor of mainstream time-namespaces Valeriy Vdovin (1): ve/proc: Added separate start time field to task_struct to show in container fs/proc/array.c | 5 +++ include/linux/sched.h | 6 +++ include/linux/time_namespace.h | 2 + include/linux/ve.h | 55 ++++++++++++++++++++++++- include/uapi/linux/prctl.h | 8 ++++ kernel/fork.c | 11 +++++ kernel/sys.c | 63 ++++++++++++++++++++++++----- kernel/time/namespace.c | 2 +- kernel/ve/ve.c | 73 +++++++++++++++++++++++++++++----- 9 files changed, 204 insertions(+), 21 deletions(-) -- 2.31.1 _______________________________________________ Devel mailing list Devel@openvz.org https://lists.openvz.org/mailman/listinfo/devel
