lkml.org 
[lkml]   [2022]   [Jun]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH 5.18 01/11] Documentation: Add documentation for Processor MMIO Stale Data
From
On 6/15/22 01:40, Greg Kroah-Hartman wrote:
> + .. list-table::
> +
> + * - 'Not affected'
> + - The processor is not vulnerable
> + * - 'Vulnerable'
> + - The processor is vulnerable, but no mitigation enabled
> + * - 'Vulnerable: Clear CPU buffers attempted, no microcode'
> + - The processor is vulnerable, but microcode is not updated. The
> + mitigation is enabled on a best effort basis.
> + * - 'Mitigation: Clear CPU buffers'
> + - The processor is vulnerable and the CPU buffer clearing mitigation is
> + enabled.
> +
> +If the processor is vulnerable then the following information is appended to
> +the above information:
> +
> + ======================== ===========================================
> + 'SMT vulnerable' SMT is enabled
> + 'SMT disabled' SMT is disabled
> + 'SMT Host state unknown' Kernel runs in a VM, Host SMT state unknown
> + ======================== ===========================================
> +

Why is list-table used in sysfs table instead of usual ASCII table in SMT
vulnerabilities list above? I think using ASCII table in both cases is enough
for the purpose.

--
An old man doll... just what I always wanted! - Clara

\
 
 \ /
  Last update: 2022-06-15 03:07    [W:0.362 / U:0.204 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site