From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from merlin.infradead.org ([205.233.59.134]:50972 "EHLO
        merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1731822AbeLQIgd (ORCPT
        <rfc822;stable@vger.kernel.org>); Mon, 17 Dec 2018 03:36:33 -0500
Date: Mon, 17 Dec 2018 09:36:06 +0100
From: Peter Zijlstra <peterz@infradead.org>
To: Barry Kauler <bkauler@gmail.com>
Cc: Jiri Kosina <jikos@kernel.org>, Andi Kleen <ak@linux.intel.com>,
        Greg KH <gregkh@linuxfoundation.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Andy Lutomirski <luto@kernel.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Tom Lendacky <thomas.lendacky@amd.com>,
        Josh Poimboeuf <jpoimboe@redhat.com>,
        Andrea Arcangeli <aarcange@redhat.com>,
        David Woodhouse <dwmw@amazon.co.uk>,
        Tim Chen <tim.c.chen@linux.intel.com>,
        Dave Hansen <dave.hansen@intel.com>,
        Casey Schaufler <casey.schaufler@intel.com>,
        Asit Mallick <asit.k.mallick@intel.com>,
        Arjan van de Ven <arjan@linux.intel.com>,
        Jon Masters <jcm@redhat.com>,
        Waiman Long <longman9394@gmail.com>,
        Dave Stewart <david.c.stewart@intel.com>,
        Kees Cook <keescook@chromium.org>, stable@vger.kernel.org
Subject: Re: SCHEDL_SMT forced on!
Message-ID: <20181217082837.GA27095@worktop>
References: <CABWT5ygnqd3-EdJ2MeE8CPo=D53NSaTps0qAR1ETX98XaO6_pA@mail.gmail.com>
 <20181216082746.GB29097@kroah.com>
 <20181216173912.GQ25620@tassilo.jf.intel.com>
 <CABWT5yjdXpcLfB1WxbK5nsgMgPsV4UATsA-ZDJhydBt_5f70QA@mail.gmail.com>
 <nycvar.YFH.7.76.1812162234390.17216@cbobk.fhfr.pm>
 <CABWT5yiDwckJ267+H3894svQyaYjGmcf94X2gvgzu-kz9rERjw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABWT5yiDwckJ267+H3894svQyaYjGmcf94X2gvgzu-kz9rERjw@mail.gmail.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Mon, Dec 17, 2018 at 05:58:11AM +0800, Barry Kauler wrote:
> 
> "SMT is a distinct feature, separate from SMP, and I think that it is
> important to keep that distinction."

Note that building a kernel without CONFIG_SCHED_SMT does _NOT_ disable
SMT. All it accomplishes is that the scheduler will not be SMT aware and
consider each SMT-sibling as a fully independent CPU.