On 6/25/20 8:34 AM, Cornelia Huck wrote:
> On Wed, 24 Jun 2020 16:22:00 -0400
> Collin Walling <walling@xxxxxxxxxxxxx> wrote:
>
>> KVM_CAP_S390_VCPU_RESETS and KVM_CAP_S390_PROTECTED needed
>> just a little bit of rst touch-up
>>
>
> Fixes: 7de3f1423ff9 ("KVM: s390: Add new reset vcpu API")
> Fixes: 04ed89dc4aeb ("KVM: s390: protvirt: Add KVM api documentation")
Do we really do that for documentation changes?
>
>> Signed-off-by: Collin Walling <walling@xxxxxxxxxxxxx>
>> ---
>> Documentation/virt/kvm/api.rst | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
>> index 056608e8f243..2d1572d92616 100644
>> --- a/Documentation/virt/kvm/api.rst
>> +++ b/Documentation/virt/kvm/api.rst
>> @@ -6134,16 +6134,17 @@ in CPUID and only exposes Hyper-V identification. In this case, guest
>> thinks it's running on Hyper-V and only use Hyper-V hypercalls.
>>
>> 8.22 KVM_CAP_S390_VCPU_RESETS
>> +-----------------------------
>>
>> -Architectures: s390
>> +:Architectures: s390
>>
>> This capability indicates that the KVM_S390_NORMAL_RESET and
>> KVM_S390_CLEAR_RESET ioctls are available.
>>
>> 8.23 KVM_CAP_S390_PROTECTED
>> +---------------------------
>>
>> -Architecture: s390
>> -
>> +:Architecture: s390
>>
>> This capability indicates that the Ultravisor has been initialized and
>> KVM can therefore start protected VMs.
>
> Reviewed-by: Cornelia Huck <cohuck@xxxxxxxxxx>
>
Attachment:
signature.asc
Description: OpenPGP digital signature
