Re: [PATCH v2 7/7] x86/irq: forward pending interrupts to new destination in fixup_irqs()

2024-06-12 Thread Jan Beulich
On 12.06.2024 13:23, Roger Pau Monné wrote: > On Tue, Jun 11, 2024 at 03:50:42PM +0200, Jan Beulich wrote: >> On 10.06.2024 16:20, Roger Pau Monne wrote: >>> @@ -2649,6 +2649,25 @@ void fixup_irqs(const cpumask_t *mask, bool verbose) >>> !cpumask_test_cpu(cpu, &cpu_online_map) && >>>

Re: [PATCH v2 7/7] x86/irq: forward pending interrupts to new destination in fixup_irqs()

2024-06-12 Thread Roger Pau Monné
On Tue, Jun 11, 2024 at 03:50:42PM +0200, Jan Beulich wrote: > On 10.06.2024 16:20, Roger Pau Monne wrote: > > fixup_irqs() is used to evacuate interrupts from to be offlined CPUs. Given > > the CPU is to become offline, the normal migration logic used by Xen where > > the > > vector in the previ

Re: [PATCH v2 7/7] x86/irq: forward pending interrupts to new destination in fixup_irqs()

2024-06-11 Thread Jan Beulich
On 10.06.2024 16:20, Roger Pau Monne wrote: > fixup_irqs() is used to evacuate interrupts from to be offlined CPUs. Given > the CPU is to become offline, the normal migration logic used by Xen where the > vector in the previous target(s) is left configured until the interrupt is > received on the

[PATCH v2 7/7] x86/irq: forward pending interrupts to new destination in fixup_irqs()

2024-06-10 Thread Roger Pau Monne
fixup_irqs() is used to evacuate interrupts from to be offlined CPUs. Given the CPU is to become offline, the normal migration logic used by Xen where the vector in the previous target(s) is left configured until the interrupt is received on the new destination is not suitable. Instead attempt to