summaryrefslogtreecommitdiff
path: root/arch/x86/kvm/Makefile
diff options
context:
space:
mode:
authorRadim Krčmář <rkrcmar@redhat.com>2014-11-20 16:43:18 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2014-11-21 20:07:33 +0300
commit6b397158d07f885154b871a15f879d25b3de7579 (patch)
treea308a01669367283fd06449bcc1587cb400c7efd /arch/x86/kvm/Makefile
parent3bf58e9ae8802bbb6af722a2e7dc4c4d21110c5a (diff)
downloadlinux-6b397158d07f885154b871a15f879d25b3de7579.tar.xz
kvm: remove IA64 ioctls
KVM ia64 is no longer present so new applications shouldn't use them. The main problem is that they most likely didn't work even before, because of a conflict in the #defines: #define KVM_SET_GUEST_DEBUG _IOW(KVMIO, 0x9b, struct kvm_guest_debug) #define KVM_IA64_VCPU_SET_STACK _IOW(KVMIO, 0x9b, void *) The argument to KVM_SET_GUEST_DEBUG is: struct kvm_guest_debug { __u32 control; __u32 pad; struct kvm_guest_debug_arch arch; }; struct kvm_guest_debug_arch { }; meaning that sizeof(struct kvm_guest_debug) == sizeof(void *) == 8 and KVM_SET_GUEST_DEBUG == KVM_IA64_VCPU_SET_STACK. KVM_SET_GUEST_DEBUG is handled in virt/kvm/kvm_main.c before even calling kvm_arch_vcpu_ioctl (which would have handled KVM_IA64_VCPU_SET_STACK), so KVM_IA64_VCPU_SET_STACK would just return -EINVAL. Signed-off-by: Radim Krčmář <rkrcmar@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/kvm/Makefile')
0 files changed, 0 insertions, 0 deletions