Unexpected Page Fault In Virtualized Environment Advisory
1–10 of 44 posts
Re: Unexpected Page Fault In Virtualized Environment Advisory
#2Someone should make a graph quantifying the number of "mitigations" and performance impacting patch work for popular Intel SKU's since release.
It would be interesting to see how many times they've patched the same processor and how much slower they are now than when they were made due to all the mitigations.
Re: Unexpected Page Fault In Virtualized Environment Advisory
#3Someone should make a graph quantifying the number of "mitigations" and performance impacting patch work for popular Intel SKU's since release. It would be interesting to see how many times they've patched the same processor and how much slower they are now than when they were made due to all the mitigations.
Do you spell "someone" A-M-D?
Re: Unexpected Page Fault In Virtualized Environment Advisory
#4This seems like the usual processor erratum causing potentially very bad things, but only in very rare conditions that no one really understands. It's not another L1TF or similar.
Re: Unexpected Page Fault In Virtualized Environment Advisory
#5Someone should make a graph quantifying the number of "mitigations" and performance impacting patch work for popular Intel SKU's since release. It would be interesting to see how many times they've patched the same processor and how much slower they are now than when they were made due to all the mitigations.
Do you spell "someone" A-M-D?
I was under the impression that AMD has their own fair share of these vulnerabilities, too. They just aren't as common in the datacenter.
Re: Unexpected Page Fault In Virtualized Environment Advisory
#6Someone should make a graph quantifying the number of "mitigations" and performance impacting patch work for popular Intel SKU's since release. It would be interesting to see how many times they've patched the same processor and how much slower they are now than when they were made due to all the mitigations.
It's workload dependent, so you're asking for a series of graphs. Not a small ask...
Phoronix has a bunch of articles where they do this but they are on a per-mitigation basis as I recall
Re: Unexpected Page Fault In Virtualized Environment Advisory
#7This seems like the usual processor erratum causing potentially very bad things, but only in very rare conditions that no one really understands. It's not another L1TF or similar.
Hence why we need open source CPUs pretty badly.
Re: Unexpected Page Fault In Virtualized Environment Advisory
#8This seems like the usual processor erratum causing potentially very bad things, but only in very rare conditions that no one really understands. It's not another L1TF or similar.
Hence why we need open source CPUs pretty badly.
I'm pretty sure that high performance open source CPUs will have their own obscure problems. Too much complexity, too many dependencies, too many possible feature interactions.
Re: Unexpected Page Fault In Virtualized Environment Advisory
#9Anyone know what conditions are required? The advisory is sparse on details.
The errata lists the same vague info: https://www.intel.com/content/dam/www/public/us/en/documents...
Re: Unexpected Page Fault In Virtualized Environment Advisory
#10Earlier quoted context omitted.
Do you spell "someone" A-M-D?
I was under the impression that AMD has their own fair share of these vulnerabilities, too. They just aren't as common in the datacenter.
AMD never had one as boneheaded as Meltdown. Intel keeps having more and more uncovered, and according to researchers who went on the record in the NYT, they are not handling reported vulnerabilities quickly or thoroughly. https://www.nytimes.com/2019/11/12/technology/intel-chip-fix...