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.
Related Semiconductor IP
- 32-bit CPU IP core supporting ISO 26262 ASIL B level functional safety for automotive applications
- Neoverse V3AE CPU
- Neoverse V3 CPU
- Neoverse N3 CPU
- Ultra-low power RISC-V microcontroller 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
- Why Choose Hard IP for Embedded FPGA in Aerospace and Defense Applications
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- Quintauris: Accelerating RISC-V Innovation for next-gen Hardware
- Say Goodbye to Limits and Hello to Freedom of Scalability in the MIPS P8700
- Why is Hard IP a Better Solution for Embedded FPGA (eFPGA) Technology?