[PATCH RFC 5/7] ARM64: KVM: Support cross type vCPU
From: Shannon Zhao
Add a capability to tell userspace that KVM supports cross type vCPU.
Add a cpu feature for userspace to set when it doesn't use host type
vCPU and kvm_vcpu_preferred_target return the host MIDR register value
so that userspace can check whether its requested vCPU type macthes the
one of physical CPU and if so, KVM will not trap ID registers even
though userspace doesn't specify -cpu host.
Guest accesses MIDR through VPIDR_EL2 so we save/restore it no matter
it's a cross type vCPU.
Signed-off-by: Shannon Zhao
---
arch/arm/kvm/arm.c | 10 --
arch/arm64/include/asm/kvm_emulate.h | 3 +++
arch/arm64/include/asm/kvm_host.h| 3 ++-
arch/arm64/include/uapi/asm/kvm.h| 1 +
arch/arm64/kvm/guest.c | 17 -
arch/arm64/kvm/hyp/sysreg-sr.c | 2 ++
include/uapi/linux/kvm.h | 1 +
7 files changed, 33 insertions(+), 4 deletions(-)
diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
index 1167678..bdceb19 100644
--- a/arch/arm/kvm/arm.c
+++ b/arch/arm/kvm/arm.c
@@ -207,6 +207,7 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
case KVM_CAP_ARM_PSCI_0_2:
case KVM_CAP_READONLY_MEM:
case KVM_CAP_MP_STATE:
+ case KVM_CAP_ARM_CROSS_VCPU:
r = 1;
break;
case KVM_CAP_COALESCED_MMIO:
@@ -809,8 +810,9 @@ static int kvm_vcpu_set_target(struct kvm_vcpu *vcpu,
{
unsigned int i;
int phys_target = kvm_target_cpu();
+ bool cross_vcpu = kvm_vcpu_has_feature_cross_cpu(init);
- if (init->target != phys_target)
+ if (!cross_vcpu && init->target != phys_target)
return -EINVAL;
/*
@@ -839,7 +841,11 @@ static int kvm_vcpu_set_target(struct kvm_vcpu *vcpu,
set_bit(i, vcpu->arch.features);
}
- vcpu->arch.target = phys_target;
+ if (!cross_vcpu)
+ vcpu->arch.target = phys_target;
+ else
+ /* Use generic ARMv8 target for cross type vcpu. */
+ vcpu->arch.target = KVM_ARM_TARGET_GENERIC_V8;
/* Now we know what it is, we can reset it. */
return kvm_reset_vcpu(vcpu);
diff --git a/arch/arm64/include/asm/kvm_emulate.h
b/arch/arm64/include/asm/kvm_emulate.h
index f5ea0ba..bca7d3a 100644
--- a/arch/arm64/include/asm/kvm_emulate.h
+++ b/arch/arm64/include/asm/kvm_emulate.h
@@ -49,6 +49,9 @@ static inline void vcpu_reset_hcr(struct kvm_vcpu *vcpu)
vcpu->arch.hcr_el2 |= HCR_E2H;
if (test_bit(KVM_ARM_VCPU_EL1_32BIT, vcpu->arch.features))
vcpu->arch.hcr_el2 &= ~HCR_RW;
+ if (test_bit(KVM_ARM_VCPU_CROSS, vcpu->arch.features))
+ /* TODO: Set HCR_TID2 and trap cache registers */
+ vcpu->arch.hcr_el2 |= HCR_TID3 | HCR_TID1 | HCR_TID0;
}
static inline unsigned long vcpu_get_hcr(struct kvm_vcpu *vcpu)
diff --git a/arch/arm64/include/asm/kvm_host.h
b/arch/arm64/include/asm/kvm_host.h
index 6034f92..d0073d7 100644
--- a/arch/arm64/include/asm/kvm_host.h
+++ b/arch/arm64/include/asm/kvm_host.h
@@ -41,10 +41,11 @@
#define KVM_MAX_VCPUS VGIC_V3_MAX_CPUS
-#define KVM_VCPU_MAX_FEATURES 4
+#define KVM_VCPU_MAX_FEATURES 5
#define KVM_REQ_VCPU_EXIT 8
+bool kvm_vcpu_has_feature_cross_cpu(const struct kvm_vcpu_init *init);
int __attribute_const__ kvm_target_cpu(void);
int kvm_reset_vcpu(struct kvm_vcpu *vcpu);
int kvm_arch_dev_ioctl_check_extension(struct kvm *kvm, long ext);
diff --git a/arch/arm64/include/uapi/asm/kvm.h
b/arch/arm64/include/uapi/asm/kvm.h
index 3051f86..7ba7117 100644
--- a/arch/arm64/include/uapi/asm/kvm.h
+++ b/arch/arm64/include/uapi/asm/kvm.h
@@ -97,6 +97,7 @@ struct kvm_regs {
#define KVM_ARM_VCPU_EL1_32BIT 1 /* CPU running a 32bit VM */
#define KVM_ARM_VCPU_PSCI_0_2 2 /* CPU uses PSCI v0.2 */
#define KVM_ARM_VCPU_PMU_V33 /* Support guest PMUv3 */
+#define KVM_ARM_VCPU_CROSS 4 /* Support cross type vCPU */
struct kvm_vcpu_init {
__u32 target;
diff --git a/arch/arm64/kvm/guest.c b/arch/arm64/kvm/guest.c
index 92abe2b..4a5ccab 100644
--- a/arch/arm64/kvm/guest.c
+++ b/arch/arm64/kvm/guest.c
@@ -308,8 +308,15 @@ int __attribute_const__ kvm_target_cpu(void)
return KVM_ARM_TARGET_GENERIC_V8;
}
+bool kvm_vcpu_has_feature_cross_cpu(const struct kvm_vcpu_init *init)
+{
+ return init->features[KVM_ARM_VCPU_CROSS / 32] &
+ (1 << (KVM_ARM_VCPU_CROSS % 32));
+}
+
int kvm_vcpu_preferred_target(struct kvm_vcpu_init *init)
{
+ bool cross_vcpu = kvm_vcpu_has_feature_cross_cpu(init);
int target = kvm_target_cpu();
if (target < 0)
@@ -323,7 +330,15 @@ int kvm_vcpu_preferred_target(struct kvm_vcpu_init *init)
* specific features available for the preferred
* target type.
*/
- init->target = (__u32)target;
+ /* If userspace wants a cross type vcpu other that host, her
Re: [PATCH RFC 5/7] ARM64: KVM: Support cross type vCPU
On Mon, Jan 16, 2017 at 05:33:32PM +0800, Shannon Zhao wrote:
> From: Shannon Zhao
>
> Add a capability to tell userspace that KVM supports cross type vCPU.
> Add a cpu feature for userspace to set when it doesn't use host type
> vCPU and kvm_vcpu_preferred_target return the host MIDR register value
> so that userspace can check whether its requested vCPU type macthes the
> one of physical CPU and if so, KVM will not trap ID registers even
> though userspace doesn't specify -cpu host.
> Guest accesses MIDR through VPIDR_EL2 so we save/restore it no matter
> it's a cross type vCPU.
>
> Signed-off-by: Shannon Zhao
> ---
> arch/arm/kvm/arm.c | 10 --
> arch/arm64/include/asm/kvm_emulate.h | 3 +++
> arch/arm64/include/asm/kvm_host.h| 3 ++-
> arch/arm64/include/uapi/asm/kvm.h| 1 +
> arch/arm64/kvm/guest.c | 17 -
> arch/arm64/kvm/hyp/sysreg-sr.c | 2 ++
> include/uapi/linux/kvm.h | 1 +
> 7 files changed, 33 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
> index 1167678..bdceb19 100644
> --- a/arch/arm/kvm/arm.c
> +++ b/arch/arm/kvm/arm.c
> @@ -207,6 +207,7 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long
> ext)
> case KVM_CAP_ARM_PSCI_0_2:
> case KVM_CAP_READONLY_MEM:
> case KVM_CAP_MP_STATE:
> + case KVM_CAP_ARM_CROSS_VCPU:
> r = 1;
> break;
> case KVM_CAP_COALESCED_MMIO:
> @@ -809,8 +810,9 @@ static int kvm_vcpu_set_target(struct kvm_vcpu *vcpu,
> {
> unsigned int i;
> int phys_target = kvm_target_cpu();
> + bool cross_vcpu = kvm_vcpu_has_feature_cross_cpu(init);
>
> - if (init->target != phys_target)
> + if (!cross_vcpu && init->target != phys_target)
> return -EINVAL;
I'm not sure we need the vcpu feature bit. I think qemu should be
allowed to try any target (if using -cpu host it will try the
kvm preferred target). kvm should check that the input target is
a known target and that it is compatible with the phys_target,
otherwise -EINVAL.
>
> /*
> @@ -839,7 +841,11 @@ static int kvm_vcpu_set_target(struct kvm_vcpu *vcpu,
> set_bit(i, vcpu->arch.features);
> }
>
> - vcpu->arch.target = phys_target;
> + if (!cross_vcpu)
> + vcpu->arch.target = phys_target;
> + else
> + /* Use generic ARMv8 target for cross type vcpu. */
> + vcpu->arch.target = KVM_ARM_TARGET_GENERIC_V8;
We want to be able to select a specific target type. So, if
init->target is approved by kvm's checking, then this should
just be
vcpu->arch.target = init->target
If, for starters, we only want to support preferred and generic,
then kvm's check is easy
init->target == phys_target || init->target == KVM_ARM_TARGET_GENERIC_V8
>
> /* Now we know what it is, we can reset it. */
> return kvm_reset_vcpu(vcpu);
> diff --git a/arch/arm64/include/asm/kvm_emulate.h
> b/arch/arm64/include/asm/kvm_emulate.h
> index f5ea0ba..bca7d3a 100644
> --- a/arch/arm64/include/asm/kvm_emulate.h
> +++ b/arch/arm64/include/asm/kvm_emulate.h
> @@ -49,6 +49,9 @@ static inline void vcpu_reset_hcr(struct kvm_vcpu *vcpu)
> vcpu->arch.hcr_el2 |= HCR_E2H;
> if (test_bit(KVM_ARM_VCPU_EL1_32BIT, vcpu->arch.features))
> vcpu->arch.hcr_el2 &= ~HCR_RW;
> + if (test_bit(KVM_ARM_VCPU_CROSS, vcpu->arch.features))
> + /* TODO: Set HCR_TID2 and trap cache registers */
> + vcpu->arch.hcr_el2 |= HCR_TID3 | HCR_TID1 | HCR_TID0;
We could optimize this a bit. For each set_one_reg of an ID register
we can check if it matches the host. If it doesn't then we flag that
we'll need that register's group trap enabled (but not the other two
groups). Here we'll then only enable traps for the necessary groups.
Maybe there's little chance that we won't always need all three
though...
> }
>
> static inline unsigned long vcpu_get_hcr(struct kvm_vcpu *vcpu)
> diff --git a/arch/arm64/include/asm/kvm_host.h
> b/arch/arm64/include/asm/kvm_host.h
> index 6034f92..d0073d7 100644
> --- a/arch/arm64/include/asm/kvm_host.h
> +++ b/arch/arm64/include/asm/kvm_host.h
> @@ -41,10 +41,11 @@
>
> #define KVM_MAX_VCPUS VGIC_V3_MAX_CPUS
>
> -#define KVM_VCPU_MAX_FEATURES 4
> +#define KVM_VCPU_MAX_FEATURES 5
>
> #define KVM_REQ_VCPU_EXIT8
>
> +bool kvm_vcpu_has_feature_cross_cpu(const struct kvm_vcpu_init *init);
> int __attribute_const__ kvm_target_cpu(void);
> int kvm_reset_vcpu(struct kvm_vcpu *vcpu);
> int kvm_arch_dev_ioctl_check_extension(struct kvm *kvm, long ext);
> diff --git a/arch/arm64/include/uapi/asm/kvm.h
> b/arch/arm64/include/uapi/asm/kvm.h
> index 3051f86..7ba7117 100644
> --- a/arch/arm64/include/uapi/asm/kvm.h
> +++ b/arch/arm64/include/uapi/asm/kvm.h
> @@ -97,6 +97,7 @@ struct kvm_regs {
> #define KVM_ARM_VCPU_EL1_32BIT 1 /* CPU running a 32bit VM */
> #de
Re: [PATCH RFC 5/7] ARM64: KVM: Support cross type vCPU
On Sat, Jan 28, 2017 at 03:47:54PM +0100, Andrew Jones wrote:
> On Mon, Jan 16, 2017 at 05:33:32PM +0800, Shannon Zhao wrote:
> > From: Shannon Zhao
> >
> > Add a capability to tell userspace that KVM supports cross type vCPU.
> > Add a cpu feature for userspace to set when it doesn't use host type
> > vCPU and kvm_vcpu_preferred_target return the host MIDR register value
> > so that userspace can check whether its requested vCPU type macthes the
> > one of physical CPU and if so, KVM will not trap ID registers even
> > though userspace doesn't specify -cpu host.
> > Guest accesses MIDR through VPIDR_EL2 so we save/restore it no matter
> > it's a cross type vCPU.
> >
> > Signed-off-by: Shannon Zhao
> > ---
> > arch/arm/kvm/arm.c | 10 --
> > arch/arm64/include/asm/kvm_emulate.h | 3 +++
> > arch/arm64/include/asm/kvm_host.h| 3 ++-
> > arch/arm64/include/uapi/asm/kvm.h| 1 +
> > arch/arm64/kvm/guest.c | 17 -
> > arch/arm64/kvm/hyp/sysreg-sr.c | 2 ++
> > include/uapi/linux/kvm.h | 1 +
> > 7 files changed, 33 insertions(+), 4 deletions(-)
> >
> > diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
> > index 1167678..bdceb19 100644
> > --- a/arch/arm/kvm/arm.c
> > +++ b/arch/arm/kvm/arm.c
> > @@ -207,6 +207,7 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long
> > ext)
> > case KVM_CAP_ARM_PSCI_0_2:
> > case KVM_CAP_READONLY_MEM:
> > case KVM_CAP_MP_STATE:
> > + case KVM_CAP_ARM_CROSS_VCPU:
> > r = 1;
> > break;
> > case KVM_CAP_COALESCED_MMIO:
> > @@ -809,8 +810,9 @@ static int kvm_vcpu_set_target(struct kvm_vcpu *vcpu,
> > {
> > unsigned int i;
> > int phys_target = kvm_target_cpu();
> > + bool cross_vcpu = kvm_vcpu_has_feature_cross_cpu(init);
> >
> > - if (init->target != phys_target)
> > + if (!cross_vcpu && init->target != phys_target)
> > return -EINVAL;
>
> I'm not sure we need the vcpu feature bit. I think qemu should be
> allowed to try any target (if using -cpu host it will try the
> kvm preferred target). kvm should check that the input target is
> a known target and that it is compatible with the phys_target,
> otherwise -EINVAL.
>
I agree. I think we just need to advertise the capability to user space
instead.
Thanks,
-Christoffer
___
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
