|
@danluu | |||||
|
BTW, if you want to try CPUID spoofing without virtualization and have a VIA processor, Agner Fog wrote this little utility:
agner.org/optimize/blog/…
Performance delta on benchmarks varies, here's an example of a ~50% gain (47%):
arstechnica.com/gadgets/2008/0… pic.twitter.com/gLK1cESeRz
|
||||||
|
||||||
|
Dan Luu
@danluu
|
7. pro |
|
This kind of thing is why the CPU startup I worked for allowed users to change the CPUID: you get huge performance gains from putting GenuineIntel in CPUID(0), but it would be a copyright violation to distribute our CPU with GenuineIntel in the CPUID
pugetsystems.com/labs/hpc/How-T… pic.twitter.com/HRduiSyypU
|
||
|
|
||
|
Dan Luu
@danluu
|
7. pro |
|
That post blames Intel, but it's not just them. NaCl forcibly crashed (and Google refused our trivial fix!!!), random drivers wouldn't work, you had to get a patched Windows installer for multiple releases of Windows (difficult in the days of CD installers), etc.
|
||
|
|
||
|
Dan Luu
@danluu
|
7. pro |
|
The Google Chromium team banning our CPUs is especially ironic in retrospect since they cited security concerns.
At the time, we were mostly shipping in-order CPUs, not vulnerable to Metldown/Spectre/etc. and of course Intel is the most vulnerable these.
twitter.com/danluu/status/…
|
||
|
|
||