From: David Woodhouse <[email protected]> A KVM_REQUEST_PER_PLANE request raised through kvm_make_vcpu_request() (kicks, mass requests) fans out to every plane twin of the vCPU, while a direct kvm_make_request() marks only the twin it was given. The per-plane Hyper-V requests use both, and a future direct caller would trip over the difference. Say so at the definition.
No functional change. Signed-off-by: David Woodhouse <[email protected]> --- include/linux/kvm_host.h | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h index ef95158ddd53..111fa3c4742c 100644 --- a/include/linux/kvm_host.h +++ b/include/linux/kvm_host.h @@ -163,6 +163,12 @@ static inline bool kvm_is_error_gpa(gpa_t gpa) #define KVM_REQUEST_NO_WAKEUP BIT(8) #define KVM_REQUEST_WAIT BIT(9) #define KVM_REQUEST_NO_ACTION BIT(10) +/* + * A KVM_REQUEST_PER_PLANE request has two scopes: raised through + * kvm_make_vcpu_request() (kicks, mass requests) it fans out to every + * plane twin of the vCPU, while a direct kvm_make_request() marks only + * the twin it was given. A direct caller must pick the twin it means. + */ #define KVM_REQUEST_PER_PLANE BIT(11) /* * Architecture-independent vcpu->requests bit members -- 2.50.1
