3 ms·
I wonder if dual-ISA processors (x86+ARM) might become a reality as a result of this sometime in the near future --- imagine a CPU that can boot in DOS-compatib
by userbinator 4y ago
I wonder if dual-ISA processors (x86+ARM) might become a reality as a result of this sometime in the near future --- imagine a CPU that can boot in DOS-compatible 16-bit realmode, transition to 32 and then 64-bit x86 protected mode, and from there, launch ARM 16/32/64-bit VMs (more like segments) to run at full native speed. As pointed out in a recent discussion here, the frontend is really the biggest difference between modern ISAs, and all instructions get broken down into uops for the backend to execute.
- deleted 4y ago[deleted]
- vegetablepotpie 4y agoOr you could go the other way around. Boot with Low power Arm, and fall back on x86 when your applications demand it. Would be the type of thing that would enable Microsoft to make a serious attempt to shift Windows to another ISA. Use the ARM ISA for the OS and newer applications, have an x86 fall back for legacy applications that require it, without needing an emulation layer. This would allay business concerns over compatibility in an industry wide transition.
- sitkack 4y agoWindows runs on Arm. https://www.tomshardware.com/how-to/install-windows-11-raspberry-pi https://www.tomshardware.com/how-to/install-windows-11-raspb... https://en.wikipedia.org/wiki/Windows_NT https://en.wikipedia.org/wiki/Windows_NT
- photonbeam 4y agoSure it does, but half the point of windows is backwards compatibility and moving to ARM devalues that too much
- userbinator 4y agoIMHO x86 has better existing facilities for different operating modes and virtualisation --- going back to the 286 protected mode descriptor types --- that make it a good fit for being the "host" of an ARM or other architecture. Also, the x86/PC boot process is far better understood and open than those of the widely differing ARM SoCs.
- AlotOfReading 4y agoHow do you figure that the x86 is more open? I can download and build all the code for an ARM system right now. There are even standards docs for most of the individual pieces. I can't do the same with any modern x86 systems and the one company trying (purisim) had to do some pretty serious reverse engineering of Intel's blobs to get there.
- pipo234 4y agoI think what @userbinator is referring to is the opaque firmware blobs and uefi surrounding typical SoCs, not the ARM software.
- NovaDudely 4y agoI feel there are a lot of folks in MS that understand how important it is to have a consistent boot process. They tried to standardize this with the boot system of Windows RT by having it map closely to that of BIOS. I think they just wanted to have ARM run like x86 by having a standard interface so they aren't building multiple different binaries for different machines. Of course this was basically bolting a good idea to an cement block dropped in the ocean, it didn't help that they had locked keys on secure boot so that users couldn't fiddle with this. A good idea done poorly.
- Symbiote 4y ago29 years ago, ARM's primary customer and original parent company released the Risc PC, which used an ARM processor but could also accept a 486 processor beside it. They were on separate cards, but it meant you could run DOS/Windows programs within the Acorn RISC OS. https://en.wikipedia.org/wiki/Risc_PC https://en.wikipedia.org/wiki/Risc_PC https://youtu.be/XI4pfjTCs3o?t=522 https://youtu.be/XI4pfjTCs3o?t=522
- lincpa 4y ago[dead]
- pavlov 4y agoThirty years ago there was the PowerPC 615 which included an x86 core. It was even pin-compatible with the Intel Pentium: ”The "PowerPC 615" is a PowerPC processor announced by IBM in 1994, but which never reached mass production. Its main feature was to incorporate an x86 core on die, thus making the processor able to natively process both PowerPC and x86 instructions.[37] An operating system running on PowerPC 615 could either choose to execute 32-bit or 64-bit PowerPC instructions, 32-bit x86 instructions or a mix of three. Mixing instructions would involve a context switch in the CPU with a small overhead. The only operating systems that supported the 615 were Minix and a special development version of OS/2.” ”was 330 mm2 large and manufactured by IBM on a 0.35 μm process. It was pin compatible with Intel's Pentium processors and comparable in speed. The processor was introduced only as a prototype and the program was killed in part by the fact that Microsoft never supported the processor.” https://en.m.wikipedia.org/wiki/PowerPC_600 https://en.m.wikipedia.org/wiki/PowerPC_600 I believe IBM had an x86 license from Intel (back from the original PC days) which allowed them to do this.
- kmeisthax 4y agoAMD originally intended Ryzen to have both x86 and ARM frontends, but the ARM frontend was cancelled after what we assume was the buyer[0] cancelled their order. Dropping ARM usermode in the middle of an x86 host[1] would be particularly weird to build architecturally, though. You'd need x86 to correctly retain ARM register state and restore it, etc. The ARM side would also need architectural extensions to generate x86-side interrupts and syscalls for paravirtualization. You'd also need to be able to handle both AArch32 and AArch64 guests on an x86 host - and hopefully that host is in long mode, right!? [0] There was speculation it might have been Amazon? [1] "Host" in the most generic case of "software that controls the live-ness of other software": i.e. kernel, hypervisor, and/or emulator
- saagarjha 4y agoI feel like what you’d probably want to implement here are extensions that make it convenient to write high-performance translators.
- pavlov 4y agoMaybe something like Transmeta, where the instruction set was designed to act as a dynamic binary translation target: https://en.wikipedia.org/wiki/Transmeta https://en.wikipedia.org/wiki/Transmeta
- xattt 4y agoTransmets promised multiple architectures, but there was never a product demonstrated in the wild.
- pavlov 4y agoI think they demonstrated Sun picoJava support alongside x86, but no products actually shipped using this architecture: https://en.wikipedia.org/wiki/PicoJava https://en.wikipedia.org/wiki/PicoJava
- sgerenser 4y ago
- dagmx 4y agoThat just sounds like there’d be so much wasted silicon for very niche use cases. I don’t see anyone doing this because the economic story wouldn’t make sense
- userbinator 4y agoThe frontend is a tiny part of a modern CPU. Caches, execution units, and registers take up much of the die.
- imhoguy 4y agoI don't think that would pay off, too exotic, there is much more flexibility with virtualization and binary translators (Rosetta).