Date: Wed, 11 Dec 2019 07:44:00 -0500 From: Ed Maste <emaste@freebsd.org> To: "O'Connor, Daniel" <darius@dons.net.au>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Disabling speculative execution mitigations Message-ID: <CAPyFy2ArNTKd6qHOAM-apJ7Hgc5Y=BciTJYbOSyesNfkA=yUpQ@mail.gmail.com> In-Reply-To: <BA7092AF-29E4-4B7B-B8D6-5CD76D99CD4A@dons.net.au> References: <C19DE24E-22CB-4E55-95CE-0A07FC8A23F5@dons.net.au> <20191206142221.GL2744@kib.kiev.ua> <BA7092AF-29E4-4B7B-B8D6-5CD76D99CD4A@dons.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 6 Dec 2019 at 22:54, O'Connor, Daniel <darius@dons.net.au> wrote: > > With respect to the man page, I find it difficult to know what a given value for each sysctl will do, as evidenced by my confusion above about IBRS. scottl recently moved these sysctls to machdep.mitigations in r355436, but they've kept the existing names and sense. So, some still have an enable control while some are disable, some report "state: inactive" while others report "active: 0". Work is ongoing now to rationalize these so that the sense is true for mitigation enabled. Backwards compatibility will be maintained for the sysctl paths in stable (e.g. hw.ibrs*) but not the interim names (machdep.mitigations.*)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2ArNTKd6qHOAM-apJ7Hgc5Y=BciTJYbOSyesNfkA=yUpQ>