Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 688e0581 authored by Dongjiu Geng's avatar Dongjiu Geng Committed by Paolo Bonzini
Browse files

KVM: Documentation: rename the capability of KVM_CAP_ARM_SET_SERROR_ESR 



In the documentation description, this capability's name is
KVM_CAP_ARM_SET_SERROR_ESR, but in the header file this
capability's name is KVM_CAP_ARM_INJECT_SERROR_ESR, so change
the documentation description to make it same.

Signed-off-by: default avatarDongjiu Geng <gengdongjiu@huawei.com>
Reported-by: default avatarAndrew Jones <drjones@redhat.com>
Reviewed-by: default avatarAndrew Jones <drjones@redhat.com>
Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
parent 63198930

Documentation/virtual/kvm/api.txt

+3 −3
Original line number Diff line number Diff line
@@ -909,10 +909,10 @@ Serviceability (RAS) Specification"). 


SError exceptions always have an ESR value. Some CPUs have the ability to

specify what the virtual SError's ESR value should be. These systems will

advertise KVM_CAP_ARM_SET_SERROR_ESR. In this case exception.has_esr will

advertise KVM_CAP_ARM_INJECT_SERROR_ESR. In this case exception.has_esr will

always have a non-zero value when read, and the agent making an SError pending

should specify the ISS field in the lower 24 bits of exception.serror_esr. If

the system supports KVM_CAP_ARM_SET_SERROR_ESR, but user-space sets the events

the system supports KVM_CAP_ARM_INJECT_SERROR_ESR, but user-space sets the events

with exception.has_esr as zero, KVM will choose an ESR.



Specifying exception.has_esr on a system that does not support it will return
@@ -4749,7 +4749,7 @@ hypercalls: 
HvFlushVirtualAddressSpace, HvFlushVirtualAddressSpaceEx,

HvFlushVirtualAddressList, HvFlushVirtualAddressListEx.



8.19 KVM_CAP_ARM_SET_SERROR_ESR

8.19 KVM_CAP_ARM_INJECT_SERROR_ESR



Architectures: arm, arm64