I would be more concerned IF the next gen CPU has this fixed. All's I know is that if Intel wants to fix the very next gen, they will need to scrap a lot of silicon that has already been finished.<br><br><br>Sent from <a href="https://protonmail.com">ProtonMail</a>, Swiss-based encrypted email.<br><br><br><br><br><br>-------- Original Message --------<br>On Jan 3, 2018, 15:35, Nathan O'Brennan < plugaz@codezilla.xyz> wrote:<blockquote class="protonmail_quote"><br><html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>
<p>I'm more curious to know which versions of Intel's upcoming chips have been fixed already. I would like to upgrade my current workstation in the next year and will stick with Intel despite any performance impact over AMD.</p>
<p><br></p>
<p><br></p>
<p>On 2018-01-03 00:43, Aaron Jones wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div> </div>
<div>I read the performance hit for Intel chips will be %35 or so after the fix. </div>
<div><br>On Jan 2, 2018, at 7:49 PM, Eric Oyen <<a href="mailto:eric.oyen@icloud.com">eric.oyen@icloud.com</a>> wrote:<br><br></div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div>so, does this mean that the UEFI might get patched first? OR, does the OS ecology have to do so first? Lastly, how much of a performance hit will this represent?
<div> </div>
<div>-eric</div>
<div>from the central offices of the Technomage Guild, the "oh look! yet another bug!" Dept.</div>
<div><br>
<div>
<div>On Jan 2, 2018, at 3:39 PM, Matthew Crews wrote:</div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><br><a href="https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/">https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/</a><br><br>In a nutshell, it is a major security flaw in Intel hardware dating back a decade that is requiring a complete kernel rewrite for every major OS (Linux, Windows, Mac, etc) in order to patch out. It cannot be patched out with a CPU microcode update. Major enough that code comments are redacted in the patches until an embargo period is expired. Also the reported fix will have a huge performance impact.<br><br>Also crucial to note is that AMD chips are not affected by this.<br><br>How the heck does something like this go unnoticed for so long?<br><br><br><br><br>Sent from <a href="https://protonmail.com/">ProtonMail</a>, Swiss-based encrypted email.<br><br></blockquote>
</div>
</div>
</div>
</blockquote>
<!-- html ignored --><br>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">---------------------------------------------------<br> PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br> To subscribe, unsubscribe, or to change your mail settings:<br> <a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a></div>
</blockquote>
<p><br></p>
</body></html></div>