sched: dom0_vcpus_pin should only affect dom0

If dom0_vcpus_pin is used, make sure the pinning is only done for
dom0 vcpus, instead of for the hardware domain (which might not be
dom0 at all!).

Suggested-by: Jan Beulich <jbeulich@suse.com>
Signed-off-by: Dario Faggioli <dfaggioli@suse.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
This commit is contained in:
Dario Faggioli authored and Jan Beulich committed 2022-08-03 12:14:01 +02:00
1 parent 2f2b76d47c
commit 01ca29f0b1
1 file changed
+1 -1
+1 -1
View File
@@ -575,7 +575,7 @@ int sched_init_vcpu(struct vcpu *v)
* Initialize affinity settings. The idler, and potentially
* domain-0 VCPUs, are pinned onto their respective physical CPUs.
*/
if ( is_idle_domain(d) || (is_hardware_domain(d) && opt_dom0_vcpus_pin) )
if ( is_idle_domain(d) || (d->domain_id == 0 && opt_dom0_vcpus_pin) )
sched_set_affinity(unit, cpumask_of(processor), &cpumask_all);
else
sched_set_affinity(unit, &cpumask_all, &cpumask_all);
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.