Drop the KVM_X86_DISABLE_VALID_EXITS definition, as it is misleading, and unused in KVM *because* it is misleading. The set of exits that can be disabled is dynamic, i.e. userspace (and KVM) must check KVM's actual capabilities.
Showing the changes to include/uapi (1 of 1 file). Show all
Unified · Split
| @@ -617,10 +617,6 @@ struct kvm_ioeventfd { · 616 unmodified lines | ||
| 617 | 617 | #define KVM_X86_DISABLE_EXITS_HLT (1 << 1) |
| 618 | 618 | #define KVM_X86_DISABLE_EXITS_PAUSE (1 << 2) |
| 619 | 619 | #define KVM_X86_DISABLE_EXITS_CSTATE (1 << 3) |
| 620 | −#define KVM_X86_DISABLE_VALID_EXITS (KVM_X86_DISABLE_EXITS_MWAIT | \ | |
| 621 | − KVM_X86_DISABLE_EXITS_HLT | \ | |
| 622 | − KVM_X86_DISABLE_EXITS_PAUSE | \ | |
| 623 | − KVM_X86_DISABLE_EXITS_CSTATE) | |
| 624 | 620 | |
| 625 | 621 | /* for KVM_ENABLE_CAP */ |
| 626 | 622 | struct kvm_enable_cap { |