Not a terrible idea. The OpenBSD team is currently wrestling with an issue where the interrupt vector code isn’t quite right and causes bad things on modern virtualization systems, but the obvious fix breaks older opteron CPUs. A “too old, go home” policy would be very helpful here. :)
Always the idea of making i386 the legacy architecture for all old i386/amd64 chips, and amd64 only for modern chips - so those old Opterons (or whatever) can pound sand. (In fact, that’s what Microsoft already did - Windows 8.1 amd64 required an instruction not available on Socket 939 Athlon 64/Opteron systems, so you were stuck on 7 or 8.0 if you wanted 64-bit Windows.)
Yeah, the writer of the article doesn’t seem to understand the amount of effort adding new CPU support to an OS is. At the same time, it is pretty hard on enterprise support to upgrade their hardware.
Not a terrible idea. The OpenBSD team is currently wrestling with an issue where the interrupt vector code isn’t quite right and causes bad things on modern virtualization systems, but the obvious fix breaks older opteron CPUs. A “too old, go home” policy would be very helpful here. :)
Always the idea of making i386 the legacy architecture for all old i386/amd64 chips, and amd64 only for modern chips - so those old Opterons (or whatever) can pound sand. (In fact, that’s what Microsoft already did - Windows 8.1 amd64 required an instruction not available on Socket 939 Athlon 64/Opteron systems, so you were stuck on 7 or 8.0 if you wanted 64-bit Windows.)
Yeah, the writer of the article doesn’t seem to understand the amount of effort adding new CPU support to an OS is. At the same time, it is pretty hard on enterprise support to upgrade their hardware.
It’s about damn time. Backwards compatibility is killing them.