[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1811031914470.3160@nanos.tec.linutronix.de>
Date: Sat, 3 Nov 2018 19:20:09 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Tim Chen <tim.c.chen@...ux.intel.com>
cc: Jiri Kosina <jikos@...nel.org>,
Tom Lendacky <thomas.lendacky@....com>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Andrea Arcangeli <aarcange@...hat.com>,
David Woodhouse <dwmw@...zon.co.uk>,
Andi Kleen <ak@...ux.intel.com>,
Dave Hansen <dave.hansen@...el.com>,
Casey Schaufler <casey.schaufler@...el.com>,
Asit Mallick <asit.k.mallick@...el.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
Jon Masters <jcm@...hat.com>,
Waiman Long <longman9394@...il.com>,
linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [Patch v4 08/18] sched: Deprecate sched_smt_present and use
cpu_smt_enabled static key
Tim,
On Tue, 30 Oct 2018, Tim Chen wrote:
> The cpu_smt_enabled static key serves identical purpose as cpu_smt_enabled
That doesn't make any sense.
> to enable SMT specific code.
>
> This patch replaces sched_smt_present in the scheduler with
> cpu_smt_enabled and deprecate sched_smt_present.
It's not deprecating it, it's replacing and removing it and thereby
breaking all architectures which select SCHED_SMT except x86.
Thanks,
tglx
Powered by blists - more mailing lists