[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1801081036100.1735@nanos>
Date: Mon, 8 Jan 2018 10:36:48 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Alexey Dobriyan <adobriyan@...il.com>
cc: Konrad Rzeszutek Wilk <konrad@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [patch V2 1/2] sysfs/cpu: Add vulnerability folder
On Mon, 8 Jan 2018, Alexey Dobriyan wrote:
> On Sun, Jan 07, 2018 at 10:50:58PM -0500, Konrad Rzeszutek Wilk wrote:
> > On Mon, Jan 08, 2018 at 01:22:04AM +0300, Alexey Dobriyan wrote:
> > > Thomas Gleixner wrote:
> > > > Create /sys/devices/system/cpu/vulnerabilities folder and files for
> > > > meltdown, spectre_v1 and spectre_v2.
> > >
> > > It is called "grep -e '^bugs' /proc/cpuinfo".
> > >
> > > kpti is deduceable from .config and /proc/cmdline .
> > > If people don't know what .config they are running, god bless them.
> >
> > It is not just for meltdown (kpti). You also have retpoline and IBRS
> > which is for spectre.
>
> If you, as kernel developer, are sure that bug is properly mitigated
> to the best of your knowledge then clear the bit from the bug mask.
Nope. The CPU is still buggy and does not become less so because we set a
mitigation into effect.
Thanks,
tglx
Powered by blists - more mailing lists