sched/isolation: Use single feature type while referring to housekeeping cpumask

Refer to housekeeping APIs using single feature types instead of flags. This prevents from passing multiple isolation features at once to housekeeping interfaces, which soon won't be possible anymore as each isolation features will have their own cpumask.

Frederic Weisbecker committed 4 years ago

Commit 04d4e661 parent c8fb9f219 files · +86 −73Browse files

Showing the changes to kernel/workqueue.c (1 of 19 files). Show all

Unified · Split

kernel/workqueue.c+2−2

@@ -6011,8 +6011,8 @@ void __init workqueue_init_early(void) · 6010 unmodified lines
6011	6011	BUILD_BUG_ON(__alignof__(struct pool_workqueue) < __alignof__(long long));
6012	6012
6013	6013	BUG_ON(!alloc_cpumask_var(&wq_unbound_cpumask, GFP_KERNEL));
6014		− cpumask_copy(wq_unbound_cpumask, housekeeping_cpumask(HK_FLAG_WQ));
6015		− cpumask_and(wq_unbound_cpumask, wq_unbound_cpumask, housekeeping_cpumask(HK_FLAG_DOMAIN));
	6014	+ cpumask_copy(wq_unbound_cpumask, housekeeping_cpumask(HK_TYPE_WQ));
	6015	+ cpumask_and(wq_unbound_cpumask, wq_unbound_cpumask, housekeeping_cpumask(HK_TYPE_DOMAIN));
6016	6016
6017	6017	pwq_cache = KMEM_CACHE(pool_workqueue, SLAB_PANIC);
6018	6018