google/gvisor

Support CLOCK_BOOTTIME

Open

#218 创建于 2019年4月29日

在 GitHub 查看
 (5 评论) (0 反应) (0 负责人)Go (12,713 star) (1,061 fork)batch import
area: compatibilitygood first issuepriority: p3type: enhancement

描述

We could likely make CLOCK_BOOTTIME equivalent to CLOCK_MONOTONIC, as CLOCK_MONOTONIC already includes time spent not running during save / restore, which is the closest thing we have to "suspend".

https://github.com/google/gvisor/blob/8f4634997bd97810a85a70b71f000378d9db2e55/pkg/sentry/kernel/timekeeper.go#L119-L129

贡献者指南

技术栈
go
领域
backend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Go programminggVisor architectureLinux clock handling
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
15
研究方向
First, examine the current implementation of CLOCK MONOTONIC in pkg/sentry/kernel/timekeeper.go (lines 119-129) to understand how it works. Then, create a similar handling for CLOCK BOOTTIME, ensuring it behaves identically to CLOCK MONOTONIC. Additionally, check if there are any other references to clock IDs in the codebase that need to be updated.