Twitter | Pretraživanje | |
Dan Luu 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
Reply Retweet Označi sa "sviđa mi se"
Dan Luu
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.
Reply Retweet Označi sa "sviđa mi se" More
Dan Luu 7. pro
Odgovor korisniku/ci @danluu
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.
Reply Retweet Označi sa "sviđa mi se"
Dan Luu 9. pro
Odgovor korisniku/ci @danluu
BTW, if you want to try CPUID spoofing without virtualization and have a VIA processor, Agner Fog wrote this little utility: Performance delta on benchmarks varies, here's an example of a ~50% gain (47%):
Reply Retweet Označi sa "sviđa mi se"
Josh Beaker 8. pro
Odgovor korisniku/ci @danluu
This makes me salty
Reply Retweet Označi sa "sviđa mi se"