diff options
author | David Woodhouse <dwmw@amazon.co.uk> | 2023-10-11 23:30:08 +0100 |
---|---|---|
committer | David Woodhouse <dwmw@amazon.co.uk> | 2023-11-06 10:03:45 +0000 |
commit | e7dbb62ff19ce55548c785d76e814e7b144e6217 (patch) | |
tree | b4db81997e73b3a792a284a5ab3a0cf7ee017408 /include | |
parent | e969f992c6562222e245dd8557f5b132a11ec29c (diff) | |
download | qemu-e7dbb62ff19ce55548c785d76e814e7b144e6217.zip qemu-e7dbb62ff19ce55548c785d76e814e7b144e6217.tar.gz qemu-e7dbb62ff19ce55548c785d76e814e7b144e6217.tar.bz2 |
i386/xen: fix per-vCPU upcall vector for Xen emulation
The per-vCPU upcall vector support had three problems. Firstly it was
using the wrong hypercall argument and would always return -EFAULT when
the guest tried to set it up. Secondly it was using the wrong ioctl() to
pass the vector to the kernel and thus the *kernel* would always return
-EINVAL. Finally, even when delivering the event directly from userspace
with an MSI, it put the destination CPU ID into the wrong bits of the
MSI address.
Linux doesn't (yet) use this mode so it went without decent testing
for a while.
Cc: qemu-stable@nongnu.org
Fixes: 105b47fdf2d0 ("i386/xen: implement HVMOP_set_evtchn_upcall_vector")
Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
Reviewed-by: Paul Durrant <paul@xen.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions