x86/viridian: EOI MSR should always happen in affected vCPU context
authorRoger Pau Monné <roger.pau@citrix.com>
Tue, 11 Jan 2022 10:42:49 +0000 (11:42 +0100)
committerJan Beulich <jbeulich@suse.com>
Tue, 11 Jan 2022 10:42:49 +0000 (11:42 +0100)
commitb8428a858aba2200abe83afa1eb7c8115979c509
treeb06cbbcf08b476f98ee3b8220fb36781056e2782
parentced5685208f4525edc3aa86f41eeaee5ccc9fe31
x86/viridian: EOI MSR should always happen in affected vCPU context

The HV_X64_MSR_EOI wrmsr should always happen with the target vCPU
as current, as there's no support for EOI'ing interrupts on a remote
vCPU.

While there also turn the unconditional assert at the top of the
function into an error on non-debug builds.

No functional change intended.

Requested-by: Jan Beulich <jbeulich@suse.com>
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Reviewed-by: Paul Durrant <paul@xen.org>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
xen/arch/x86/hvm/viridian/synic.c