Page MenuHomeFreeBSD

linprocfs: Decode tsc_invariant CPU feature
ClosedPublic

Authored by dchagin on Jun 22 2022, 11:41 PM.
Tags
None
Referenced Files
F163197884: D35554.id107520.diff
Mon, Jul 20, 11:39 PM
Unknown Object (File)
Sat, Jul 18, 3:27 AM
Unknown Object (File)
Wed, Jul 15, 12:34 PM
Unknown Object (File)
Sat, Jul 11, 9:51 PM
Unknown Object (File)
Jun 1 2026, 4:55 PM
Unknown Object (File)
May 17 2026, 11:08 AM
Unknown Object (File)
May 17 2026, 10:25 AM
Unknown Object (File)
May 16 2026, 8:39 PM
Subscribers

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

does Linux report it like this? I couldn't find "invariant_tsc" in the Linux repo

does Linux report it like this? I couldn't find "invariant_tsc" in the Linux repo

yep, it should be constant_tsc.
our tsc_is_invariant is the same Linux X86_FEATURE_CONSTANT_TSC (which is syntetic bit in the x86_cap_flags)
x86_cap_flags is generated by mkcapflags.sh abd used by procfs to generate CPU flags.

I think that check for invariant_tsc in the /proc/cpuinfo is a bug in glibc tests suite code.
Glibc call cpuid() in the get_extended_indices() and treats CPUID.80000007H:EDX[8] as INVARIANT_TSC and check that invariant_tsc exists in the /proc/cpuinfo, while it is not exposed by the Linux kernel.

This revision was not accepted when it landed; it landed in state Needs Review.Jun 29 2022, 7:39 AM
This revision was automatically updated to reflect the committed changes.