Hello, On Sat, Mar 07, 2020 at 11:06:47AM -0500, Mathieu Desnoyers wrote: > Looking into solving this, one key issue seems to get in the way: cpuset > appear to care about not allowing to create a cpuset which has no currently > active CPU where to run, e.g.: ... > Clearly, there is an intent that cpusets take the active mask into > account to prohibit creating an empty cpuset, but nothing prevents > cpu hotplug from creating an empty cpuset. > > I wonder how to solve this inconsistency ? Please try cpuset in cgroup2. It shouldn't have those issues. Thanks. -- tejun
