| Message ID | 1529960309-2513-3-git-send-email-gengdongjiu@huawei.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Hi Dongjiu Geng, This patch doesn't apply on v4.18-rc2. Documentation/virtual/kvm/api.txt already has a 8.18 section. I guess you based this on v4.17. For posting patches, please use the latest 'rc' from Linus' tree, (or the maintainer's tree listed in MAINTAINERS for the tree you are targeting if the maintainer has started to pick up patches). Thanks, James On 25/06/18 21:58, Dongjiu Geng wrote: > For the arm64 RAS Extension, user space can inject a virtual-SError > with specified ESR. So user space needs to know whether KVM support > to inject such SError, this interface adds this query for this capability. > > KVM will check whether system support RAS Extension, if supported, KVM > returns true to user space, otherwise returns false. > diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt > index 3732097..86b3808 100644 > --- a/Documentation/virtual/kvm/api.txt > +++ b/Documentation/virtual/kvm/api.txt > @@ -4628,3 +4628,14 @@ Architectures: s390 > This capability indicates that kvm will implement the interfaces to handle > reset, migration and nested KVM for branch prediction blocking. The stfle > facility 82 should not be provided to the guest without this capability. > + > +8.14 KVM_CAP_ARM_SET_SERROR_ESR > + > +Architectures: arm, arm64 > + > +This capability indicates that userspace can specify the syndrome value reported > +to the guest OS when guest takes a virtual SError interrupt exception. > +If KVM has this capability, userspace can only specify the ISS field for the ESR > +syndrome, it can not specify the EC field which is not under control by KVM. > +If this virtual SError is taken to EL1 using AArch64, this value will be reported > +in ISS filed of ESR_EL1.
Hi James, On 2018/6/29 23:58, James Morse wrote: > Hi Dongjiu Geng, > > This patch doesn't apply on v4.18-rc2. > > Documentation/virtual/kvm/api.txt already has a 8.18 section. I guess you based > this on v4.17. Yes, indeed I based on v4.17. > > For posting patches, please use the latest 'rc' from Linus' tree, (or the > maintainer's tree listed in MAINTAINERS for the tree you are targeting if the > maintainer has started to pick up patches). Ok, I will rebase it using the latest 'rc' from Linus' tree. thanks for the reminder. > > > Thanks, > > James > > > On 25/06/18 21:58, Dongjiu Geng wrote: >> For the arm64 RAS Extension, user space can inject a virtual-SError >> with specified ESR. So user space needs to know whether KVM support >> to inject such SError, this interface adds this query for this capability. >> >> KVM will check whether system support RAS Extension, if supported, KVM >> returns true to user space, otherwise returns false. > > >> diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt >> index 3732097..86b3808 100644 >> --- a/Documentation/virtual/kvm/api.txt >> +++ b/Documentation/virtual/kvm/api.txt >> @@ -4628,3 +4628,14 @@ Architectures: s390 >> This capability indicates that kvm will implement the interfaces to handle >> reset, migration and nested KVM for branch prediction blocking. The stfle >> facility 82 should not be provided to the guest without this capability. >> + >> +8.14 KVM_CAP_ARM_SET_SERROR_ESR >> + >> +Architectures: arm, arm64 >> + >> +This capability indicates that userspace can specify the syndrome value reported >> +to the guest OS when guest takes a virtual SError interrupt exception. >> +If KVM has this capability, userspace can only specify the ISS field for the ESR >> +syndrome, it can not specify the EC field which is not under control by KVM. >> +If this virtual SError is taken to EL1 using AArch64, this value will be reported >> +in ISS filed of ESR_EL1. > > > > > . >
diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt index 3732097..86b3808 100644 --- a/Documentation/virtual/kvm/api.txt +++ b/Documentation/virtual/kvm/api.txt @@ -4628,3 +4628,14 @@ Architectures: s390 This capability indicates that kvm will implement the interfaces to handle reset, migration and nested KVM for branch prediction blocking. The stfle facility 82 should not be provided to the guest without this capability. + +8.14 KVM_CAP_ARM_SET_SERROR_ESR + +Architectures: arm, arm64 + +This capability indicates that userspace can specify the syndrome value reported +to the guest OS when guest takes a virtual SError interrupt exception. +If KVM has this capability, userspace can only specify the ISS field for the ESR +syndrome, it can not specify the EC field which is not under control by KVM. +If this virtual SError is taken to EL1 using AArch64, this value will be reported +in ISS filed of ESR_EL1. diff --git a/arch/arm64/kvm/reset.c b/arch/arm64/kvm/reset.c index f7a80dc..20e919a 100644 --- a/arch/arm64/kvm/reset.c +++ b/arch/arm64/kvm/reset.c @@ -77,6 +77,9 @@ int kvm_arch_dev_ioctl_check_extension(struct kvm *kvm, long ext) case KVM_CAP_ARM_PMU_V3: r = kvm_arm_support_pmu_v3(); break; + case KVM_CAP_ARM_INJECT_SERROR_ESR: + r = cpus_have_const_cap(ARM64_HAS_RAS_EXTN); + break; case KVM_CAP_SET_GUEST_DEBUG: case KVM_CAP_VCPU_ATTRIBUTES: case KVM_CAP_VCPU_EVENTS: diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h index b02c41e..e88f976 100644 --- a/include/uapi/linux/kvm.h +++ b/include/uapi/linux/kvm.h @@ -948,6 +948,7 @@ struct kvm_ppc_resize_hpt { #define KVM_CAP_S390_BPB 152 #define KVM_CAP_GET_MSR_FEATURES 153 #define KVM_CAP_HYPERV_EVENTFD 154 +#define KVM_CAP_ARM_INJECT_SERROR_ESR 155 #ifdef KVM_CAP_IRQ_ROUTING