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
- Configurable CPU tailored precisely to your needs
- Multi-core capable 64-bit RISC-V CPU with vector extensions
- Multi-core capable 32-bit RISC-V CPU with vector extensions
- 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
Related Blogs
- From ARM7 to such a Large CPU cores Port-Folio
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- LPDDR6: The Next-Generation LPDDR Device Standard and How It Differs from LPDDR5
- High Bandwidth Memory Evolution from First Generation HBM to the Latest HBM4
Latest Blogs
- A Repeatable Framework for Hardware Security Assurance
- Inside the SiFive Performance™ P570 Gen 3: High Performance Efficiency for Next-Generation Consumer and Commercial Applications
- What the steam engine can teach us about modern chip design
- Automotive silicon in the era of AI, functional safety, and cybersecurity
- JPEG XS Officially Joins GenICam, The Machine Vision Standard Managed By EMVA