aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/scripts/gdb/linux/utils.py
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2024-12-13 14:36:25 -0500
committerPaolo Bonzini <pbonzini@redhat.com>2024-12-22 13:00:25 -0500
commit9a1dfeff4414112ce89652a5017538016ccd656c (patch)
treef926f879797c1e205c8ded3c0fec1efb516db116 /scripts/gdb/linux/utils.py
parentMerge tag 'kvm-x86-fixes-6.13-rcN' of https://github.com/kvm-x86/linux into HEAD (diff)
downloadwireguard-linux-9a1dfeff4414112ce89652a5017538016ccd656c.tar.xz
wireguard-linux-9a1dfeff4414112ce89652a5017538016ccd656c.zip
KVM: x86: clear vcpu->run->hypercall.ret before exiting for KVM_EXIT_HYPERCALL
QEMU up to 9.2.0 is assuming that vcpu->run->hypercall.ret is 0 on exit and it never modifies it when processing KVM_EXIT_HYPERCALL. Make this explicit in the code, to avoid breakage when KVM starts modifying that field. This in principle is not a good idea... It would have been much better if KVM had set the field to -KVM_ENOSYS from the beginning, so that a dumb userspace that does nothing on KVM_EXIT_HYPERCALL would tell the guest it does not support KVM_HC_MAP_GPA_RANGE. However, breaking userspace is a Very Bad Thing, as everybody should know. Reported-by: Binbin Wu <binbin.wu@linux.intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions