| Message ID | 20201124105953.39325-5-ravi.bangoria@linux.ibm.com (mailing list archive) |
|---|---|
| State | Not Applicable |
| Headers | show |
| Series | KVM: PPC: Power10 2nd DAWR enablement | expand |
| Context | Check | Description |
|---|---|---|
| snowpatch_ozlabs/apply_patch | warning | Failed to apply on branch powerpc/merge (7c94b5d4e9d328a69d43a11d7e3dfd7a6d762cb6) |
| snowpatch_ozlabs/apply_patch | warning | Failed to apply on branch powerpc/next (3cea11cd5e3b00d91caf0b4730194039b45c5891) |
| snowpatch_ozlabs/apply_patch | warning | Failed to apply on branch linus/master (d5beb3140f91b1c8a3d41b14d729aefa4dcc58bc) |
| snowpatch_ozlabs/apply_patch | warning | Failed to apply on branch powerpc/fixes (b6b79dd53082db11070b4368d85dd6699ff0b063) |
| snowpatch_ozlabs/apply_patch | warning | Failed to apply on branch linux-next (d9137320ac06f526fe3f9a3fdf07a3b14201068a) |
| snowpatch_ozlabs/apply_patch | fail | Failed to apply to any branch |
On Tue, Nov 24, 2020 at 04:29:53PM +0530, Ravi Bangoria wrote: > Introduce KVM_CAP_PPC_DAWR1 which can be used by Qemu to query whether > kvm supports 2nd DAWR or not. This should be described in Documentation/virt/kvm/api.rst. Strictly speaking, it should be a capability which is disabled by default, so the guest can only do the H_SET_MODE to set DAWR[X]1 if it has been explicitly permitted to do so by userspace (QEMU). This is because we want as little as possible of the VM configuration to come from the host capabilities rather than from what userspace configures. So what we really need here is for this to be a capability which can be queried by userspace to find out if it is possible, and then enabled by userspace if it wants. See how KVM_CAP_PPC_NESTED_HV is handled for example. Paul.
diff --git a/arch/powerpc/kvm/powerpc.c b/arch/powerpc/kvm/powerpc.c index 13999123b735..48763fe59fc5 100644 --- a/arch/powerpc/kvm/powerpc.c +++ b/arch/powerpc/kvm/powerpc.c @@ -679,6 +679,9 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext) !kvmppc_hv_ops->enable_svm(NULL); break; #endif + case KVM_CAP_PPC_DAWR1: + r = cpu_has_feature(CPU_FTR_DAWR1); + break; default: r = 0; break; diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h index f6d86033c4fa..0f32d6cbabc2 100644 --- a/include/uapi/linux/kvm.h +++ b/include/uapi/linux/kvm.h @@ -1035,6 +1035,7 @@ struct kvm_ppc_resize_hpt { #define KVM_CAP_LAST_CPU 184 #define KVM_CAP_SMALLER_MAXPHYADDR 185 #define KVM_CAP_S390_DIAG318 186 +#define KVM_CAP_PPC_DAWR1 187 #ifdef KVM_CAP_IRQ_ROUTING
Introduce KVM_CAP_PPC_DAWR1 which can be used by Qemu to query whether kvm supports 2nd DAWR or not. Signed-off-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com> --- arch/powerpc/kvm/powerpc.c | 3 +++ include/uapi/linux/kvm.h | 1 + 2 files changed, 4 insertions(+)