From: Greg KH <gregkh@linuxfoundation.org>
To: Barry Kauler <bkauler@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jiri Kosina <jkosina@suse.cz>,
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>,
Andi Kleen <ak@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: Sun, 16 Dec 2018 09:27:46 +0100 [thread overview]
Message-ID: <20181216082746.GB29097@kroah.com> (raw)
In-Reply-To: <CABWT5ygnqd3-EdJ2MeE8CPo=D53NSaTps0qAR1ETX98XaO6_pA@mail.gmail.com>
On Sun, Dec 16, 2018 at 02:21:55PM +0800, Barry Kauler wrote:
> Mr Gleixner,
> I was upset when I compiled 4.14.87 found that SCHED_SMT had been
> forced on. At the time, I just reported it to my blog, and posted a
> question about it to a couple of forums, and stayed with an earlier
> kernel.
>
> However, when 4.14.88 came out, and still the same situation, alarm
> bells went off, and I looked through the kernel changelog. Found it,
> 4.14.86:
>
> "x86/Kconfig: Select SCHED_SMT if SMP enabled"
>
> Then:
>
> "CONFIG_SCHED_SMT is enabled by all distros, so there is not a real point to
> have it configurable. ..."
>
> ...that is a lie. It would be correct to state that is true of the
> distros you use, and presumably also for all of you guys who signed
> off on it.
>
> Puppy Linux is an example of a distro that has mostly not had
> SCHED_SMT enabled. Ditto for most of the forks of Puppy. Two distros
> that I currently maintain, Quirky and EasyOS (easyos.org) have SMP
> enabled but not SCHED_SMT.
>
> The difference between them is important, they should remain
> independently settable. I am so surprised that all of you guys went
> along with forcing it on.
Is having this option enabled causing a problem for you? Does it cause
slowdowns or runtime issues?
thanks,
greg k-h
next prev parent reply other threads:[~2018-12-16 8:27 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 [this message]
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
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=20181216082746.GB29097@kroah.com \
--to=gregkh@linuxfoundation.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=jcm@redhat.com \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=longman9394@gmail.com \
--cc=luto@kernel.org \
--cc=peterz@infradead.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.