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.
Support CLOCK_BOOTTIME · google/gvisor#218 | Good First Issue