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
- I3C Controller IP – I3C / I2C Slave, Configure User Registers, no CPU Host Required
- I3C Controller IP – I3C / I2C Slave, SCL Clock only, Configure User Registers, no CPU Host Required
- RISC-V CPU IP
- 32-bit CPU IP core supporting ISO 26262 ASIL B level functional safety for automotive applications
- Neoverse V3AE CPU
Related Blogs
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- 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
- Reducing design cycle time for semiconductor startups: The path from MVP to commercial viability