From: Dario Faggioli Date: Wed, 3 Aug 2022 10:14:01 +0000 (+0200) Subject: sched: dom0_vcpus_pin should only affect dom0 X-Git-Tag: archive/raspbian/4.17.0-1+rpi1^2~33^2~352 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=01ca29f0b17a50a94b0e232ba276c32e95d80ae3;p=xen.git 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 Signed-off-by: Dario Faggioli Reviewed-by: Jan Beulich --- diff --git a/xen/common/sched/core.c b/xen/common/sched/core.c index f689b55783..a066c629cb 100644 --- a/xen/common/sched/core.c +++ b/xen/common/sched/core.c @@ -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);