lkml.org 
[lkml]   [2018]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] clarify how insecure CPU is
On Mon, 8 Jan 2018, Pavel Machek wrote:

>
> First, what is going on with X86_BUG_AMD_E400 and X86_BUG_AMD_APIC_C1E
> ? They seem to refer to the same bug, perhaps comment should mention
> that? (Do we need two flags for one bug?)
>
> Next, maybe X86_BUG_CPU_INSECURE is a bit too generic? This seems to
> address "Meltdown" problem, but not "Spectre". Should it be limited to
> PPro and newer Intel CPUs?
>
> Should another erratum be added for "Spectre"? This is present even on
> AMD CPUs, but should not be present in 486, maybe Pentium, and some
> Atom chips?
>
> Plus... is this reasonable interface?
>
> bugs : cpu_insecure

We've renamed it to meltdown already and added spectre_v1/v2 bits for the
rest of the mess.

\
 
 \ /
  Last update: 2018-01-14 23:18    [W:0.049 / U:0.184 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site