Can look up guides specific to the CPU to figure out what a sane initial target / voltage for it is. Auto voltage probably uses too much (tuned to work with even terrible CPUs and it varies a lot) but might as well start with that for simplicity, can drop it manually later.
-
-
now that I look at it, clearcpuid only seems to affect /proc/cpuinfo, cpuid(1) still shows AVX as enabled... weird.
-
Maybe noxsave works properly since it seems like it must for the reason
@RichFelker pointed out. -
I've rebooted with noxsave and AVX is still present in cpuid outputs (and I confirmed that the kernel uses fxsave via dmesg). weird.
-
It traps if it's actually used though, right?
-
ah yes, I figured it out. kernel never does cpuid emulation, only kvm can do that. and xsave has a bit in CR4.
-
I thought there was a MSR to mask cpuid..?
-
I don't think Linux has any code that uses it.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.