[PATCH RESEND 02/27] Drivers: hv: utils: run polling callback always in interrupt context

From: Olaf Hering All channel interrupts are bound to specific VCPUs in the guest at the point channel is created. While currently, we invoke the polling function on the correct CPU (the CPU to which the channel is bound to) in some cases we may run the polling function in a non-interrupt

[PATCH RESEND 02/27] Drivers: hv: utils: run polling callback always in interrupt context

From: Olaf Hering All channel interrupts are bound to specific VCPUs in the guest at the point channel is created. While currently, we invoke the polling function on the correct CPU (the CPU to which the channel is bound to) in some cases we may run the polling function in a

[PATCH RESEND 02/27] Drivers: hv: utils: run polling callback always in interrupt context

From: Olaf Hering All channel interrupts are bound to specific VCPUs in the guest at the point channel is created. While currently, we invoke the polling function on the correct CPU (the CPU to which the channel is bound to) in some cases we may run the polling function in a non-interrupt

[PATCH RESEND 02/27] Drivers: hv: utils: run polling callback always in interrupt context

From: Olaf Hering All channel interrupts are bound to specific VCPUs in the guest at the point channel is created. While currently, we invoke the polling function on the correct CPU (the CPU to which the channel is bound to) in some cases we may run the polling function in a