Commit b0f46280 authored by Janosch Frank's avatar Janosch Frank Committed by Christian Borntraeger
Browse files

Documentation/virt/kvm/api.rst: Explain rc/rrc delivery 



Let's explain in which situations the rc/rrc will set in struct
kvm_pv_cmd so it's clear that the struct members should be set to
0. rc/rrc are independent of the IOCTL return code.

Signed-off-by: default avatarJanosch Frank <frankja@linux.ibm.com>
Acked-by: default avatarClaudio Imbrenda <imbrenda@linux.ibm.com>
Link: https://lore.kernel.org/r/20220517163629.3443-12-frankja@linux.ibm.com


Message-Id: <20220517163629.3443-12-frankja@linux.ibm.com>
Signed-off-by: default avatarChristian Borntraeger <borntraeger@linux.ibm.com>
parent 437cfd71

Documentation/virt/kvm/api.rst

+8 −0
Original line number Diff line number Diff line
@@ -5127,6 +5127,14 @@ into ESA mode. This reset is a superset of the initial reset. 
	__u32 reserved[3];

  };



**Ultravisor return codes**

The Ultravisor return (reason) codes are provided by the kernel if a

Ultravisor call has been executed to achieve the results expected by

the command. Therefore they are independent of the IOCTL return

code. If KVM changes `rc`, its value will always be greater than 0

hence setting it to 0 before issuing a PV command is advised to be

able to detect a change of `rc`.



**cmd values:**



KVM_PV_ENABLE