4 ms·
Anyone know what in particular the 486SX had that the 386 didn’t to make keeping only the former alive practical? Unfortunately the kernel mailing list link in
by twoodfin 6y ago
Anyone know what in particular the 486SX had that the 386 didn’t to make keeping only the former alive practical? Unfortunately the kernel mailing list link in the zdnet article appears to be rotted away.
- BruiseLee 6y agoI believe 386 did not have certain "atomic" instructions like CMPXCHG or XADD. So in order to support 386, the kernel had to have special versions of all locking primitives just for 386.
- projektfu 6y agoBasic multitasking (CMPXCHG) and cache management instructions.
- jabl 6y agoHere's a working link: http://lkml.iu.edu/hypermail/linux/kernel/1212.1/01152.html http://lkml.iu.edu/hypermail/linux/kernel/1212.1/01152.html From that link: x86, 386 removal: Remove CONFIG_CMPXCHG x86, 386 removal: Remove CONFIG_XADD x86, 386 removal: Remove CONFIG_BSWAP x86, 386 removal: Remove CONFIG_INVLPG x86, 386 removal: Remove CONFIG_X86_WP_WORKS_OK x86, 386 removal: Remove CONFIG_X86_POPAD_OK