1.6 KiB
title, type, source, source_url, author, handle, post_id, date, archived, draft, tags, description, in_reply_to
| title | type | source | source_url | author | handle | post_id | date | archived | draft | tags | description | in_reply_to | |||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Renovating CPU clock code. | archive | https://x.com/NOTimothyLottes/status/2060730425929080874 | NOTimothyLottes | NOTimothyLottes | 2060730425929080874 | 2026-05-30 | 2026-08-25 | false |
|
Renovating CPU clock code. |
Source
- URL: https://x.com/NOTimothyLottes/status/2060730425929080874
- Author: NOTimothyLottes (@NOTimothyLottes)
- Posted: 2026-05-30 14:29:54
Thread
1/ @NOTimothyLottes ^2060730425929080874
Renovating CPU clock code. I'm assuming x86-64 TSC is always >= 1 GHz so that conversion of clock counter diff to nanoseconds is simply a MUL instruction fetching the RDX high 64-bit result (of the 128-bit computed). But figuring out how to do the inline asm was a pain.
2/ @NOTimothyLottes ^2060742129190568413
Looks like NtQuerySystemInformation() with SystemHypervisorSharedPageInformation (aka 0xc5) gives 64-bit scalar for TSC that converts time to units of 10 MHz. So the smart way is to work in units of TSC, then do a subtraction of TSC terms, then MULHI to get {ms, us, or ns} time
3/ @NOTimothyLottes ^2060752921092833490
https://gist.github.com/pmttavara/6f06fc5c7679c07375483b06bb77430c - A great reference for getting TSC scaling multipliers on Linux and Windows