On Mon, 17 Dec 2018, Barry Kauler wrote: > Being forced to do it on the kernel commandline is not satisfactory. If > it can be done there, why not also retain it as a configuration option? It's not realy the same thing. SMT can be turned on and off dynamically either during boot, or during runtime (by offlining/onlining SMT siblings). If scheduler is compiled as SMT unaware, then it stays so "forever". So you can't populate that kernel to SMT and non-SMT system configurations, you can't migrate the running system between SMT and non-SMT systems, etc. -- Jiri Kosina SUSE Labs
