What The Tech 333: x86 Emulation on ARM

Posted on November 23, 2016 by Paul Thurrott in Podcasts, What The Tech with 2 Comments

In this episode of What the Tech, Andrew Zarian and I discuss Microsoft’s reportedly plans to bring x86 emulation to ARM-based versions of Windows 10, what we know about the Windows VR headsets, and Andrew’s review of the VOYO VBook V3 Ultrabook.

Running time: 58:22

Download and subscribe

Download this episode and subscribe to What the Tech


Enjoy What the Tech on YouTube

Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (2)

2 responses to “What The Tech 333: x86 Emulation on ARM”

  1. 538

    I'm getting a similar sort of feeling with this as I did with the iOS / Android mobile bridges that were announced a while back. It'd certainly be nice to have, but it seems like a hefty technological challenge (to do right) so it's one thing to say your working on it and another to have it working well, and I can't see if being the saviour of WP as some people seem to be hoping. Still, something interesting to look out for in the medium term.  

  2. 8870

    Don't get me wrong here, I like you guys. But when you venture into topics for CPU technologies you have less expertise. This podcasts discussion on ARM versus Intel is a good example.

    Intel processors are and have always been built for maximum computational type of jobs. You touched on that idea in this same show, Intel CPUs are less interesting because they are measured on gen to gen enhancements and everyone knows that yardstick. ARM is not judged in the same way and if they were let's be honest they would look pretty bad by comparison. If ARM was more competitive, their power and cost advantage would quickly disappear. Talking about replacing Intel with ARM is baloney (or baloney-ish) in the context you used in this show.

    ARM has done really well for phones because the computational needs are less and the degree of integration required for a phone favors their ecosystem, that is their real advantage. Integration is the key that helped them win phones.

    Ironically Intel's big weakness in phones is related to their greatest strength, they rely on their own fabs. They can make a competitive CPU for phones in capabilities and power, but the problem is that for Intel to be competitive in the phone market they have to right size not just the CPU and chipset logic but they also need to build a silicon ecosystem that offers competitive silicon logic blocks for everything else a phone needs. And that logic does not all run on Intel fab processes. That's why they failed.

    Paring down the x86 CPU for phones is straightforward and very doable. The problem that in order to be successful they have to integrate everything else into their unique fab ecosystem and that is a huge problem. Intel fabs are world class for digital logic, power, reliability, and quality. They are not so good with mixed-signal applications (think radios and tricky IO). Even Intel makes Ethernet and radio chips at external Fabs, why is that? The key problem of mixed signal cell libraries is proving to be too difficult and too expensive (even for Intel). 

    The better question to ask is how well ARM will perform in areas such as servers and consumer PCs, how difficult it will be to migrate the massive investment of software, and will the end products be as flexible running apps? Windows RT shows the OS can run on ARM, but migration is a lot harder than it looks and you don't get the benefits of the Intel ecosystem.  That's the trade-off, not the CPU.

    P.S. Can you increase the amount of space for comments? Your web tool only shows 4-lines at a time... blech!

Leave a Reply