Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S965175AbeAJNxr (ORCPT <rfc822;ralf@linux-mips.org> + 1 other);
        Wed, 10 Jan 2018 08:53:47 -0500
Received: from Galois.linutronix.de ([146.0.238.70]:55853 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S964999AbeAJNxp (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 10 Jan 2018 08:53:45 -0500
Date: Wed, 10 Jan 2018 14:53:28 +0100 (CET)
From: Thomas Gleixner <tglx@linutronix.de>
To: "Van De Ven, Arjan" <arjan.van.de.ven@intel.com>
cc: David Woodhouse <dwmw2@infradead.org>,
        Andrea Arcangeli <aarcange@redhat.com>,
        Jiri Kosina <jikos@kernel.org>,
        "Mallick, Asit K" <asit.k.mallick@intel.com>,
        Peter Zijlstra <peterz@infradead.org>,
        "Hansen, Dave" <dave.hansen@intel.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Linus Torvalds <torvalds@linuxfoundation.org>,
        "x86@kernel.org" <x86@kernel.org>, Borislav Petkov <bp@alien8.de>,
        Tim Chen <tim.c.chen@linux.intel.com>,
        Andi Kleen <ak@linux.intel.com>,
        Greg KH <gregkh@linuxfoundation.org>,
        Andy Lutomirski <luto@kernel.org>
Subject: RE: [patch RFC 5/5] x86/speculation: Add basic speculation control
 code
In-Reply-To: <0575AF4FD06DD142AD198903C74E1CC87A57235B@ORSMSX103.amr.corp.intel.com>
Message-ID: <alpine.DEB.2.20.1801101452100.1919@nanos>
References: <20180110092234.GY29822@worktop.programming.kicks-ass.net>  <1515576479.22302.81.camel@infradead.org>  <20180110115419.GA9706@redhat.com>  <1515585534.22302.122.camel@infradead.org>  <20180110120158.GB9706@redhat.com>  <1515586174.22302.126.camel@infradead.org>
  <20180110121755.GD9706@redhat.com>  <1515587384.22302.132.camel@infradead.org>  <20180110124119.GG9706@redhat.com>  <alpine.LRH.2.00.1801101343540.27010@gjva.wvxbf.pm>  <20180110125710.GH9706@redhat.com> <1515589641.22302.145.camel@infradead.org>
 <alpine.DEB.2.20.1801101424180.1919@nanos> <0575AF4FD06DD142AD198903C74E1CC87A57235B@ORSMSX103.amr.corp.intel.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>

On Wed, 10 Jan 2018, Van De Ven, Arjan wrote:
> > So here is the simple list of questions all to be answered with YES or
> > NO. I don't want to see any of the 'but, though ...'. We all know by now
> > that it's CPU dependent and slow and whatever and that IBRS_ATT will be in
> > future CPUs. So get your act together and tell a clear YES or NO.

> > 2) Does toggle mode of IBRS require retpoline ?
> 
> NO
> 
> > 
> > 3) Does toggle mode of IBRS require RSB stuffing ?
> 
> Only for the VM exit case

Ok.

> > 
> > 4) Exist CPUs which require IBRS to be selected automatically ?
> 
> I do not understand your question exactly

Whether the kernel should enable IBRS by default on certain models. And if
yes, which ones.

Thanks,

	tglx