Paolo Bonzini e4fc23bad8 KVM: x86: remove KVM_X86_OP_NULL and mark optional kvm_x86_ops
The original use of KVM_X86_OP_NULL, which was to mark calls
that do not follow a specific naming convention, is not in use
anymore.  Instead, let's mark calls that are optional because
they are always invoked within conditionals or with static_call_cond.
Those that are _not_, i.e. those that are defined with KVM_X86_OP,
must be defined by both vendor modules or some kind of NULL pointer
dereference is bound to happen at runtime.

Reviewed-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2022-02-18 12:31:27 -05:00
..
2022-01-23 06:20:44 +02:00
2022-01-23 06:20:44 +02:00
2022-02-11 12:10:57 -05:00
2022-01-23 06:20:44 +02:00
2022-01-23 06:20:44 +02:00
2022-01-23 06:20:44 +02:00
2022-01-23 06:20:44 +02:00
2022-01-19 11:15:19 +02:00
2022-02-05 09:55:59 -08:00
2022-01-19 11:15:19 +02:00
2022-01-19 11:15:19 +02:00
2022-01-23 06:20:44 +02:00
2022-01-23 06:20:44 +02:00
2022-02-05 00:58:25 -05:00
2022-01-23 06:20:44 +02:00
2022-01-23 06:20:44 +02:00
2022-01-23 06:20:44 +02:00