[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH v2 06/10] xen/common: Restore IRQ affinity when hotplugging a pCPU
Non-boot pCPUs are being hot-unplugged during the system suspend to RAM and hotplugged during the resume. When non-boot pCPUs are hot-unplugged the interrupts that were targeted to them are migrated to the boot pCPU. On suspend, each guest could have its own wake-up devices/interrupts (passthrough) that could trigger the system resume. These interrupts could be targeted to a non-boot pCPU, e.g. if the guest's vCPU is pinned to a non-boot pCPU. Due to the hot-unplug of non-boot pCPUs during the suspend such interrupts will be migrated from non-boot pCPUs to the boot pCPU (this is fine). However, when non-boot pCPUs are hotplugged on resume, these interrupts are not migrated back to non-boot pCPUs, i.e. IRQ affinity is not restored on resume (this is wrong). This patch adds the restoration of IRQ affinity when a pCPU is hotplugged. Signed-off-by: Mirela Simonovic <mirela.simonovic@xxxxxxxxxx> --- CC: George Dunlap <george.dunlap@xxxxxxxxxxxxx> CC: Dario Faggioli <dfaggioli@xxxxxxxx> --- Changes in v2: -Instead of checking whether the affinity was broken check whether vcpu's processor has changed in order to trigger restoring of the IRQ affinity -Fix commit message --- xen/common/schedule.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/xen/common/schedule.c b/xen/common/schedule.c index 343ab6306e..c37ef4846d 100644 --- a/xen/common/schedule.c +++ b/xen/common/schedule.c @@ -692,6 +692,7 @@ void restore_vcpu_affinity(struct domain *d) for_each_vcpu ( d, v ) { spinlock_t *lock; + unsigned int old_cpu = v->processor; ASSERT(!vcpu_runnable(v)); @@ -724,6 +725,9 @@ void restore_vcpu_affinity(struct domain *d) lock = vcpu_schedule_lock_irq(v); v->processor = SCHED_OP(vcpu_scheduler(v), pick_cpu, v); spin_unlock_irq(lock); + + if ( old_cpu != v->processor ) + sched_move_irqs(v); } domain_update_node_affinity(d); -- 2.13.0 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |