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!
Date: Mon, 17 Dec 2018 09:36:06 +0100 [thread overview]
Message-ID: <20181217082837.GA27095@worktop> (raw)
In-Reply-To: <CABWT5yiDwckJ267+H3894svQyaYjGmcf94X2gvgzu-kz9rERjw@mail.gmail.com>
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.
prev parent reply other threads:[~2018-12-17 8:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 6:21 SCHEDL_SMT forced on! Barry Kauler
2018-12-16 8:27 ` Greg KH
2018-12-16 17:39 ` Andi Kleen
2018-12-16 21:29 ` Barry Kauler
2018-12-16 21:37 ` Jiri Kosina
2018-12-16 21:58 ` Barry Kauler
2018-12-16 22:01 ` Jiri Kosina
2018-12-16 22:12 ` Jiri Kosina
2018-12-16 22:26 ` Barry Kauler
2018-12-16 22:13 ` Barry Kauler
2018-12-16 22:17 ` Jiri Kosina
2018-12-16 22:31 ` Arjan van de Ven
2018-12-17 8:36 ` Peter Zijlstra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181217082837.GA27095@worktop \
--to=peterz@infradead.org \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=asit.k.mallick@intel.com \
--cc=bkauler@gmail.com \
--cc=casey.schaufler@intel.com \
--cc=dave.hansen@intel.com \
--cc=david.c.stewart@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jcm@redhat.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=longman9394@gmail.com \
--cc=luto@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.