aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/iio/trigger/stm32-timer-trigger.c
diff options
context:
space:
mode:
authorSam Bobroff <[email protected]>2017-09-26 06:47:04 +0000
committerRadim Krčmář <[email protected]>2017-10-03 15:58:16 +0000
commit2fb1e946450a4fef74bb72f360555f7760d816f0 (patch)
treea2cd3794460739e885ca9456c2e3c81f3213a357 /drivers/iio/trigger/stm32-timer-trigger.c
parentLinux 4.14-rc3 (diff)
downloadkernel-2fb1e946450a4fef74bb72f360555f7760d816f0.tar.gz
kernel-2fb1e946450a4fef74bb72f360555f7760d816f0.zip
KVM: PPC: Book3S: Fix server always zero from kvmppc_xive_get_xive()
In KVM's XICS-on-XIVE emulation, kvmppc_xive_get_xive() returns the value of state->guest_server as "server". However, this value is not set by it's counterpart kvmppc_xive_set_xive(). When the guest uses this interface to migrate interrupts away from a CPU that is going offline, it sees all interrupts as belonging to CPU 0, so they are left assigned to (now) offline CPUs. This patch removes the guest_server field from the state, and returns act_server in it's place (that is, the CPU actually handling the interrupt, which may differ from the one requested). Fixes: 5af50993850a ("KVM: PPC: Book3S HV: Native usage of the XIVE interrupt controller") Cc: [email protected] Signed-off-by: Sam Bobroff <[email protected]> Acked-by: Benjamin Herrenschmidt <[email protected]> Signed-off-by: Radim Krčmář <[email protected]>
Diffstat (limited to 'drivers/iio/trigger/stm32-timer-trigger.c')
0 files changed, 0 insertions, 0 deletions