10 ms·
Hell Freezes Over as AMD and Intel Come Together for x86
- fsflover 2y agoWhen wil we be able to completely disable the Intel ME and AMD PSP on modern devices?
- throwaway48476 2y agoWhy do you want to remove the backdoor?
- mysterydip 2y agoThey must have something to hide.
- froh 2y agobackdoor schmackdoor --- it's a little BSD for your safety and security how dare you slander the poor thing with such a heinous label. tsk.
- transpute 2y agohttps://news.ycombinator.com/item?id=15830545 https://news.ycombinator.com/item?id=15830545
- fsflover 2y ago"Disabled" is far from completely removed. Closed, proprietary software with unlimited system access says it's disabled. Do you trust that?
- tredre3 2y agoWhy are you moving the goalposts? Your question was specifically how to completely disable it, not how to lobby AMD/Intel into removing the feature from the silicon...
- BoingBoomTschak 2y agoHis point is still valid: how do you know it's disabled other than "just trust me"? If I was the NSA, I'd work very close with OEMs to bug the rare order with "Intel vPro™ - ME Inoperable, Custom Order" checked; bit like https://arstechnica.com/tech-policy/2014/05/photos-of-an-nsa-upgrade-factory-show-cisco-router-getting-implant/ https://arstechnica.com/tech-policy/2014/05/photos-of-an-nsa...
- fluoridation 2y agoBut by that measure, how do you know the platform doesn't have yet another remote control feature that you don't know about? Do you trust the platform or don't you?
- snerbles 2y agoUltimately, you can't. From Ken Thompson's "Reflections on Trusting Trust" [0], written in 1984: > The moral is obvious. You can't trust code that you did not totally create yourself. (Especially code from companies that employ people like me.) No amount of source-level verification or scrutiny will protect you from using untrusted code. In demonstrating the possibility of this kind of attack, I picked on the C compiler. I could have picked on any program-handling program such as an assembler, a loader, or even hardware microcode. As the level of program gets lower, these bugs will be harder and harder to detect. A well-installed microcode bug will be almost impossible to detect. [0] https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_Ref...
- fluoridation 2y ago"Trust" in the security sense. https://en.wikipedia.org/wiki/Trusted_system https://en.wikipedia.org/wiki/Trusted_system You can trust a system by accepting that if it is owned, you are owned. If you don't trust it you instead protect it with a system that you do trust. For example, if you don't trust any x86 system you would not make them face the Internet. You would put them behind a trusted firewall. But you have to decide whether you trust a system or not. If you trust it then you have to believe it when it reports a certain feature is disabled. If you don't trust it to begin with then it doesn't matter if it's disabled or not. Your security shouldn't be relying on it anyway.
- rob74 2y agoTo me it looks like the two finally decided to cooperate because it's in their common interest to stop (or rather, delay) the x86 architecture's slide into irrelevance?
- burnte 2y agoPeople have been talking about the irrelevance of x86 since the 80s. I remember the early 90s when "Intel is doomed" was daily news and opinion fodder.
- joshdavham 2y agoDon’t you think this time things may be different though? Many new computers, cloud platforms and even the iPad I’m typing on right now have/are switching to ARM and away from x86.
- Dalewyn 2y agoARM should be more worried about getting usurped by China!RISC-V than x86 getting usurped by, well, anything. x86 still powers most of how we actually get stuff done.
- echelon 2y agoBoth should worry about getting usurped by RISC-V. x86 is getting cornered by ARM in consumer and data center. RISC-V is gunning for ARM. While ARM is open-ish, RISC-V is more open than both. When you're not the market leader, that's the strategy to become market leader. And it certainly helps that a major world power is putting in enormous energy to make their architecture the dominant alternative to "Western" architectures.
- leptons 2y agoThere still aren't ARM chips that can compete with the processing power of the highest-end x86 chips, if power consumption isn't an issue. It's nice that your iPad has an ARM chip in it, but nobody is going to be using an iPad for real workloads. And when it comes to available software, x86 just laughs at ARM.
- bhouston 2y agoThis is mostly a recognition of the shared threat that ARM poses to both AMD and Intel. ARM took embedded first, then mobile, then gaming (on mobile and handhelds), then Macs, and now it is making real inroads into Windows laptops (e.g. Snapdragon X Elite) and servers (e.g. Graviton.) The next shoe to drop would be a high-end gaming PC that can take an NVIDIA or AMD graphics card powered by a Snapdragon X Elite-like ARM chip. Another shoe to drop would be a super-computer powered by ARM chips instead of x86. I don't think that has happened yet? After that, the last refuge of x86 is in legacy software that hasn't been natively ported to ARM. But there will be fewer and fewer cases of this as the years go by. For now I think it will be mostly games. x86 is under serious threat.
- short_sells_poo 2y agoAnd here I thought windows on arm was increasingly sliding into irrelevance as nobody is buying it.
- Wytwwww 2y ago> After that, the last refuge of x86 It's not like ARM has taken over those markets yet. Snapdragon X is fine but nothing special compared AMD/Intel chips. I think we just might have a pretty distorted view of ARM vs x86 because of Apple. They are just much better at designing ARM chips than anyone else (including both Qualcomm and especially ARM itself). Servers is kind of a mixed story as well. There is nothing wrong with other companies trying to disrupt AMD/Intel duopoly and hopefully we'll get lower prices and more innovation because of that but calling x86 dead is a bit premature at this point..
- bhouston 2y ago> Snapdragon X is fine but nothing special compared AMD/Intel chips. The issue is that ARM is now fine for Windows. Until Snapdragon, ARM was actually pretty crap outside of Apple. This is a huge step. Qualcomm acquired a lot of the original Apple team for the M1 via Nuvia and I expect them to be able to execute at least decently going forward. Apparently they are selling because they have better battery life than Intel/AMD laptops according to this: https://www.techpowerup.com/324301/battery-life-is-driving-sales-of-qualcomm-snapdragon-copilot-pcs-not-ai https://www.techpowerup.com/324301/battery-life-is-driving-s... > Servers is kind of a mixed story as well. Graviton is 30% cheap for the performance (e.g. performance adjusted price.) It is a no brainer for a lot of workflows, especially given so many developers are actually building on ARM machines in the first place. I want my servers to be 30% cheaper. > There is nothing wrong with other companies trying to disrupt AMD/Intel duopoly and hopefully we'll get lower prices and more innovation because of that but calling x86 dead is a bit premature at this point.. Qualcomm is exploring acquiring Intel. A company who got its value from ARM is looking to take over the historic leader in x86 - doesn't that tell you something? https://www.reuters.com/markets/deals/qualcomm-approached-intel-about-takeover-recent-days-wsj-reports-2024-09-20/ https://www.reuters.com/markets/deals/qualcomm-approached-in... The writing is on the wall. x86 isn't dead and it won't be dead anytime soon, but it definitely in its twilight period.
- mikece 2y agoIs there any chance that Intel and AMD could merge to face the threats from ARM and Nvidia?
- jitl 2y agoI’m not sure regulators would look too favorably on that merger, but also what would that give AMD? Enormous R&D costs and a mid-tier foundry business that’s losing money and unable to support their product lines.
- jbverschoor 2y agoIntel is worth roughly it’s assets. An Intel-AMD merger would make sense, but it’s only extension of extinction if they don’t migrate from x86
- knowitnone 2y agoYou're calling it over before it's over. Is there a chance? Sure, just like there's a chance ARM could become extinct.
- jbverschoor 2y agoIt was already over 4 years ago. No cpu, no gpu, no 5G, no ultra low power or anything else that’s interesting
- vegadw 2y agoI hope this means better ISA & extension consistency going forward and a push to make tools to adopt the extensions too. One of the bigger issues for x86-64 as an ISA is that nobody wants to compile to support features that not everyone will have, but picking what to use at run-time isn't easy either, so it makes everything slower than it needs to be.
- dlojudice 2y agoPat Gelsinger and Lisa Su interview: https://www.youtube.com/watch?v=7y32wpDhIGM https://www.youtube.com/watch?v=7y32wpDhIGM
- fluoridation 2y agoGod, Su is barely intelligible. Her noise gate is turned up to hell.
- ChrisArchitect 2y ago[dupe] https://news.ycombinator.com/item?id=41851104 https://news.ycombinator.com/item?id=41851104
- MrHamburger 2y agoTo disrupt any kind of x86 dominance ARM Motherboard manufacturers will first need to get their UEFI and ACPI support working first, otherwise their boards are nothing more than one-purpose toys running only a specific build of a system.
- M95D 2y agoBut ACPI and UEFI won't solve anything. We already have devicetrees that are open and free vs. ACPI and UEFI that are just binary blobs. It would be even worse than Broadcom blobs on Raspberry Pi. What you probably want is less variability in SoC devices. Now each chip has a different SDHCI, different USB, different UART and different I2c, each needing a different driver. x86 only has 2: the Intel variant or the AMD variant.
- MrHamburger 2y agoOpen and free devicetree is absolutely useless if it needs to be part of OS image. The purpose of ACPI and UEFI is to have single booting mechanism with standardized device enumeration which is available directly on the hardware. If you need to have a random file in your OS image to actually boot on board X and if you have a file for board Y then OS will just crash boot loop, then your solution is useless for 90%+ of users because people are not going to build their own Linux distributions for their own hardware. If you know what board are you booting on, then you can load correct hardware drivers for everything else. But that's not going to work without UEFI and ACPI.
- M95D 2y agoAnd why does it have to be UEFI and ACPI? Just put u-boot and devicetree on an EEPROM - the same EEPROM/flash that would be needed for UEFI.
- MrHamburger 2y agoBecause it is a standard. Your proposed solution is ad-hoc which will work on your device(s), but nowhere else. Just make a mind experiment - Is flash memory SPI or parallel NAND? What if it is a Parallel NOR? Is EEPROM I2C? On which address? Which I2C controller should you use if there is more than one? Is EEPROM SPI? Which SPI controller you should use? How you should configure your SPI/I2C/Parallel controller? Which registers, on which addresses? On which GPIO pins is your memory device connected? You would still need some board specific mini device tree in your OS to resolve this issue. That's the reason why we have UEFI booting first and letting board manufacturer resolve it and then just providing a communication layer to make standardized queries without knowing all those questions above.
- tapanjk 2y ago> The initial advisory list includes Broadcom, Dell, Google, HP, Lenovo, Meta, Microsoft, Oracle, Red Hat, Linus Torvalds, and Tim Sweeny. Two individuals along with multi-billion dollar corporations. Curious why the organizations that these individuals represent were not included instead?
- dielll 2y agoHere rooting for Risc-V