[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240617181315.z3mbmv6hv5frtu6a@desk>
Date: Mon, 17 Jun 2024 11:13:15 -0700
From: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
To: Andrew Cooper <andrew.cooper3@...rix.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
daniel.sneddon@...ux.intel.com, tony.luck@...el.com,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
linux-perf-users@...r.kernel.org,
Josh Poimboeuf <jpoimboe@...nel.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Ricardo Neri <ricardo.neri-calderon@...ux.intel.com>,
"Liang, Kan" <kan.liang@...ux.intel.com>
Subject: Re: [PATCH PATCH 8/9] x86/bugs: Declutter vulnerable CPU list
On Mon, Jun 17, 2024 at 10:38:32AM +0100, Andrew Cooper wrote:
[...]
> > + VULNBL_INTEL(IVYBRIDGE, SRBDS),
> > + VULNBL_INTEL(HASWELL, SRBDS),
> > + VULNBL_INTEL(HASWELL_L, SRBDS),
> > + VULNBL_INTEL(HASWELL_G, SRBDS),
> > + VULNBL_INTEL(HASWELL_X, MMIO),
> > + VULNBL_INTEL(BROADWELL_D, MMIO),
> > + VULNBL_INTEL(BROADWELL_G, SRBDS),
> > + VULNBL_INTEL(BROADWELL_X, MMIO),
> > + VULNBL_INTEL(BROADWELL, SRBDS),
> > + VULNBL_INTEL(SKYLAKE_X, MMIO | RETBLEED | GDS),
> > + VULNBL_INTEL(SKYLAKE_L, MMIO | RETBLEED | GDS | SRBDS),
> > + VULNBL_INTEL(SKYLAKE, MMIO | RETBLEED | GDS | SRBDS),
> > + VULNBL_INTEL(KABYLAKE_L, MMIO | RETBLEED | GDS | SRBDS),
> > + VULNBL_INTEL(KABYLAKE, MMIO | RETBLEED | GDS | SRBDS),
> > + VULNBL_INTEL(CANNONLAKE_L, RETBLEED),
> > + VULNBL_INTEL(ICELAKE_L, MMIO | MMIO_SBDS | RETBLEED | GDS),
> > + VULNBL_INTEL(ICELAKE_D, MMIO | GDS),
> > + VULNBL_INTEL(ICELAKE_X, MMIO | GDS),
> > + VULNBL_INTEL(COMETLAKE, MMIO | MMIO_SBDS | RETBLEED | GDS),
> > + VULNBL_INTEL(TIGERLAKE_L, GDS),
> > + VULNBL_INTEL(TIGERLAKE, GDS),
> > + VULNBL_INTEL(LAKEFIELD, MMIO | MMIO_SBDS | RETBLEED),
> > + VULNBL_INTEL(ROCKETLAKE, MMIO | RETBLEED | GDS),
> > + VULNBL_INTEL(ALDERLAKE, RFDS),
> > + VULNBL_INTEL(ALDERLAKE_L, RFDS),
> > + VULNBL_INTEL(RAPTORLAKE, RFDS),
> > + VULNBL_INTEL(RAPTORLAKE_P, RFDS),
> > + VULNBL_INTEL(RAPTORLAKE_S, RFDS),
> > + VULNBL_INTEL(ATOM_GRACEMONT, RFDS),
> > + VULNBL_INTEL(ATOM_TREMONT, MMIO | MMIO_SBDS | RFDS),
> > + VULNBL_INTEL(ATOM_TREMONT_D, MMIO | RFDS),
> > + VULNBL_INTEL(ATOM_TREMONT_L, MMIO | MMIO_SBDS | RFDS),
> > + VULNBL_INTEL(ATOM_GOLDMONT, RFDS),
> > + VULNBL_INTEL(ATOM_GOLDMONT_D, RFDS),
> > + VULNBL_INTEL(ATOM_GOLDMONT_PLUS, RFDS),
>
> Take the opportunity to realign and fix this ?
I assume by also adding a tab to all the other entries?
Powered by blists - more mailing lists