diff options
| author | Jiangshan Yi <yijiangshan@kylinos.cn> | 2026-09-01 11:32:01 +0800 |
|---|---|---|
| committer | Wei Liu <wei.liu@kernel.org> | 2026-09-13 22:34:59 +0000 |
| commit | 0cdd57a4c56115af5d736b5b2d9310ad91494abc (patch) | |
| tree | a6f7b43ea233c7ff24a662c5f05133086b8a4278 /tools/lib/python/kdoc/python_version.py | |
| parent | 32ea0a33e3a0fb7c10c601b43e1b2f6c06a3f5fd (diff) | |
| download | linux-next-0cdd57a4c56115af5d736b5b2d9310ad91494abc.tar.gz linux-next-0cdd57a4c56115af5d736b5b2d9310ad91494abc.zip | |
x86/hyperv: Fix stale comments after stimer message mode removal
The removal of stimer message mode in commit be0cfab740e5 ("clocksource:
hyper-v: Remove support for stimer interrupts in message mode") left a
few comments out of date. hv_stimer_setup_percpu_clockev() picked up two
typos ("afters", "to allows"), and the hv_synic_suspend() comment still
references the deleted hv_stimer_legacy_cleanup(), the legacy non-Direct
Mode configuration, and clockevents_unbind_device(), which is no longer
on the cleanup path.
Update the typos and rewrite the hv_synic_suspend() comment to describe
the current Direct Mode path: non-boot CPU stimers are cleaned up via
the cpuhp teardown callback hv_stimer_cleanup(), and CPU0's stimer is
left alone because it is harmless (interrupts stay disabled across the
suspend/resume window) and is shut down later by the timekeeping code.
Signed-off-by: Jiangshan Yi <yijiangshan@kylinos.cn>
Reviewed-by: Michael Kelley <mhklinux@outlook.com>
Signed-off-by: Wei Liu <wei.liu@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions