6 Lessons from the CPU Meltdown
The chief technologist of a computer hardware and software company shares some basic principles for plugging the security gaps in the next Meltdown or Spectre.
In January, Intel surprised us all with the news that it's Meltdown and Spectre CPU firmware patches were no good. The instructions were to immediately cease distributing and uploading the firmware patches.
Unfortunately, people who had downloaded the patch could not uninstall it, creating endless reboots and unpredictable system behavior. Now even AMD has joined the debacle as it faces class action lawsuits over how it responded to the flaws.
Some OEMs were better prepared than others with dedicated labs and processes to test patches before they are implemented. Others, not so much. But there are a few things we can do to help protect our customers and ourselves.
To read the full article, click here
Related Semiconductor IP
- RISC-V CPU IP
- Data Movement Engine - Best in class multi-core high-performance AI-enabled RISC-V Automotive CPU for ADAS, AVs and SDVs
- Ultra-low power consumption out-of-order commercial-grade 64-bit RISC-V CPU IP
- CPU IP Following the RVA23 Profile, supporting RVV1.0 and all extensions of Vector Crypto
- High-performance RISC-V CPU
Related Blogs
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- iSuppli raises 2010 foundry forecast; interesting lessons to learn for India from China’s story!
- Want to know the three lessons for GLOBALFOUNDRIES from its 28nm high-K, metal-gate development?
- From ARM7 to such a Large CPU cores Port-Folio
Latest Blogs
- Breaking the Silence: What Is SoundWire‑I3S and Why It Matters
- What It Will Take to Build a Resilient Automotive Compute Ecosystem
- The Blind Spot of Semiconductor IP Sales
- Scalable I/O Virtualization: A Deep Dive into PCIe’s Next Gen Virtualization
- UEC-LLR: The Future of Loss Recovery in Ethernet for AI and HPC