[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a65e8b13-2452-edae-9b59-35c833a04530@intel.com>
Date: Thu, 4 Jan 2018 09:13:02 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Andrea Arcangeli <aarcange@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>
Cc: Andrew Cooper <andrew.cooper3@...rix.com>,
"Woodhouse, David" <dwmw@...zon.co.uk>,
"pavel@....cz" <pavel@....cz>,
"tim.c.chen@...ux.intel.com" <tim.c.chen@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"andi@...stfloor.org" <andi@...stfloor.org>,
"gnomes@...rguk.ukuu.org.uk" <gnomes@...rguk.ukuu.org.uk>,
"gregkh@...ux-foundation.org" <gregkh@...ux-foundation.org>
Subject: Re: Avoid speculative indirect calls in kernel
On 01/04/2018 08:25 AM, Andrea Arcangeli wrote:
> It's only where SPEC_CTRL is missing and only IBPB_SUPPORT is
> available, that ibrs 0 ibpb 2 is the only option to fix variant#2 for
> good.
Could you help us decode what "ibrs 0 ibpb 2" means to you?
Powered by blists - more mailing lists