News for hackers. Stuff that matters.
Re:The x86 CPU: From 4004 to 486 by colejohnson66 on Wednesday November 18, 2026 @06:00PM (#50553580)
Virtualization is a big thing. But it's also just effort. Keeping the cruft in costs nothing - the HDL doesn't change. It works any everyone knows how to deal with it.

This isn't like an operating system where backwards compatibility takes effort. Since this sits on the boot path, it takes more effort to remove a wart than to just leave it.

I know us developers like to ask "why not fix the wart", but that wart hurts no one.

Re:The x86 CPU: From 4004 to 486 by skissane on Wednesday November 18, 2026 @06:16PM (#50553733)
Actually, I just learnt something...

Only the BIOS init code cares about which mode the BSP starts in

But the OS cares about what mode the APs start in. Most operating systems use INIT-SIPI-SIPI, which starts the APs in real mode.

If an OS uses ACPI 6.4 Multiprocessor Wakeup Mailbox instead, then UEFI does the INIT-SIPI-SIPI on the APs, puts them in 64-bit long mode, then hands that to the OS. However, few bare metal UEFI implementations actually implement it, it is mainly implemented by hypervisors to support confidential VMs.

So, Intel/AMD could make the BSP start in 32-bit protected mode, with minimal BIOS code changes; but the APs would still need to start in 16-bit real mode. They couldn't make the APs start in a different mode until they got everyone to move off INIT-SIPI-SIPI.

Re:The x86 CPU: From 4004 to 486 by userbinator on Thursday November 19, 2026 @12:09AM (#50556289)
The amount of logic required for real mode is absolutely tiny compared to the rest of the CPU, and changing it in any way does have the very real risk of breaking something unintentionally:

https://www.os2museum.com/wp/will-the-real-real-mode-please-...

http://www.os2museum.com/wp/maximum-overkill/