KVM: arm64: Make CPU ID registers writable by userspace
Subsystems (5)
v2 cover KVM: arm64: Make CPU ID registers writable by userspace
In KVM/arm64, values of ID registers for a guest are mostly same as its host's values except for bits for feature that KVM doesn't support and for opt-in features that userspace didn't configure. Userspace can use KVM_SET_ONE_REG to a set ID register value, but it fails if userspace attempts to modify the register value.
This patch series adds support to allow userspace to modify a value of ID registers (as long as KVM can support features that are indicated in the registers) so userspace can have more control of configuring and unconfiguring features for guests.
The patch series affects both VHE or non-VHE including protected VMs for now but should be changed not to affect for protected VMs, which will have a different way of configuring ID registers [1] based on its different requirements.
There was a patch series that tried to achieve the same thing [2]. A few snippets of codes in this series were inspired by or came from [2].
The initial value of ID registers for a vCPU will be the host's value with bits cleared for unsupported features and for opt-in features that were not configured. So, the initial value userspace can see (via KVM_GET_ONE_REG) is the upper limit that can be set for the register. Any requests to change the value that conflicts with opt-in features' configuration will fail.
When a guest tries to use a CPU feature that is not exposed to the guest, trapping it (to emulate a real CPU's behavior) would generally be a desirable behavior (when it's possible with no or little side effects). The later patches in the series add codes for this. Only features that can be trapped independently will be trapped by this series though.
The series is based on v5.15 with the patch series [3] applied.
v2:
- Remove unnecessary line breaks. [Andrew]
- Use @params for comments. [Andrew]
- Move arm64_check_features to arch/arm64/kvm/sys_regs.c and change that KVM specific feature check function. [Andrew]
- Remove unnecessary raz handling from __set_id_reg. [Andrew]
- Remove sys_val field from the initial id_reg_info and add it in the later patch. [Andrew]
- Call id_reg->init() from id_reg_info_init(). [Andrew]
- Fix cpuid_feature_cap_perfmon_field() to convert 0xf to 0x0 (and use it in the following patches).
- Change kvm_vcpu_first_run_init to set has_run_once to false when kvm_id_regs_consistency_check() fails.
- Add a patch to introduce id_reg_info for ID_AA64MMFR0_EL1, which requires special validity checking for TGran*_2 fields.
- Add patches to introduce id_reg_info for ID_DFR1_EL1 and ID_MMFR0_EL1, which are required due to arm64_check_features implementation change.
- Add a new argument, which is a pointer to id_reg_info, for id_reg_info's validate()
v1: https://lore.kernel.org/all/[email protected]/
[1] https://lore.kernel.org/kvmarm/[email protected]/
[2] https://lore.kernel.org/kvm/[email protected]/
[3] https://lore.kernel.org/kvmarm/[email protected]/
Reiji Watanabe (28):
KVM: arm64: Add has_reset_once flag for vcpu
KVM: arm64: Save ID registers' sanitized value per vCPU
KVM: arm64: Introduce struct id_reg_info
KVM: arm64: Keep consistency of ID registers between vCPUs
KVM: arm64: Make ID_AA64PFR0_EL1 writable
KVM: arm64: Make ID_AA64PFR1_EL1 writable
KVM: arm64: Make ID_AA64ISAR0_EL1 writable
KVM: arm64: Make ID_AA64ISAR1_EL1 writable
KVM: arm64: Make ID_AA64MMFR0_EL1 writable
KVM: arm64: Hide IMPLEMENTATION DEFINED PMU support for the guest
KVM: arm64: Make ID_AA64DFR0_EL1 writable
KVM: arm64: Make ID_DFR0_EL1 writable
KVM: arm64: Make ID_DFR1_EL1 writable
KVM: arm64: Make ID_MMFR0_EL1 writable
KVM: arm64: Make MVFR1_EL1 writable
KVM: arm64: Make ID registers without id_reg_info writable
KVM: arm64: Add consistency checking for frac fields of ID registers
KVM: arm64: Introduce KVM_CAP_ARM_ID_REG_WRITABLE capability
KVM: arm64: Use vcpu->arch cptr_el2 to track value of cptr_el2 for VHE
KVM: arm64: Use vcpu->arch.mdcr_el2 to track value of mdcr_el2
KVM: arm64: Introduce framework to trap disabled features
KVM: arm64: Trap disabled features of ID_AA64PFR0_EL1
KVM: arm64: Trap disabled features of ID_AA64PFR1_EL1
KVM: arm64: Trap disabled features of ID_AA64DFR0_EL1
KVM: arm64: Trap disabled features of ID_AA64MMFR1_EL1
KVM: arm64: Trap disabled features of ID_AA64ISAR1_EL1
KVM: arm64: Activate trapping of disabled CPU features for the guest
KVM: arm64: selftests: Introduce id_reg_test
Documentation/virt/kvm/api.rst | 8 + arch/arm64/include/asm/cpufeature.h | 2 +- arch/arm64/include/asm/kvm_arm.h | 32 + arch/arm64/include/asm/kvm_host.h | 18 +- arch/arm64/include/asm/sysreg.h | 2 + arch/arm64/kvm/arm.c | 31 +- arch/arm64/kvm/debug.c | 13 +- arch/arm64/kvm/hyp/vhe/switch.c | 14 +- arch/arm64/kvm/reset.c | 4 + arch/arm64/kvm/sys_regs.c | 1236 ++++++++++++++-- include/uapi/linux/kvm.h | 1 + tools/arch/arm64/include/asm/sysreg.h | 1 + tools/testing/selftests/kvm/.gitignore | 1 + tools/testing/selftests/kvm/Makefile | 1 + .../selftests/kvm/aarch64/id_reg_test.c | 1296 +++++++++++++++++ 15 files changed, 2508 insertions(+), 152 deletions(-) create mode 100644 tools/testing/selftests/kvm/aarch64/id_reg_test.c
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 1/28 KVM: arm64: Add has_reset_once flag for vcpu
Introduce 'has_reset_once' flag in kvm_vcpu_arch, which indicates if the vCPU reset has been done once, for later use.
--- arch/arm64/include/asm/kvm_host.h | 2 ++ arch/arm64/kvm/reset.c | 4 ++++ 2 files changed, 6 insertions(+)
arch/arm64/include/asm/kvm_host.h +2 -0
@@ -384,6 +384,7 @@ struct kvm_vcpu_arch {u64 last_steal;gpa_t base; } steal; +bool has_reset_once; };/* Pointer to the vcpu's SVE FFR for sve_{save,load}_state() */
@@ -449,6 +450,7 @@ struct kvm_vcpu_arch {#define vcpu_has_sve (vcpu) (system_supports_sve() && \ ((vcpu)->arch.flags & KVM_ARM64_GUEST_HAS_SVE)) +#define vcpu_has_reset_once (vcpu) ((vcpu)->arch.has_reset_once)#ifdef CONFIG_ARM64_PTR_AUTH #define vcpu_has_ptrauth (vcpu) \
arch/arm64/kvm/reset.c +4 -0
@@ -305,6 +305,10 @@ int kvm_reset_vcpu(struct kvm_vcpu *vcpu)if (loaded)kvm_arch_vcpu_load (vcpu,smp_processor_id ());preempt_enable (); + +if (!ret && !vcpu->arch.has_reset_once) + vcpu->arch.has_reset_once = true; +return ret; }
Signature · 1 line
2.33.1.1089.g2158813163f-goog
Re: [RFC PATCH v2 01/28] KVM: arm64: Add has_reset_once flag for vcpu
Quoted 4 lines · Reiji Watanabe
Introduce '
has_reset_once' flag inkvm_vcpu_arch, which indicates if the vCPU reset has been done once, for later use.Signed-off-by Reiji Watanabe <[email protected]>
Quoted 43 lines
--- arch/arm64/include/asm/kvm_host.h | 2 ++ arch/arm64/kvm/reset.c | 4 ++++ 2 files changed, 6 insertions(+)arch/arm64/include/asm/kvm_host.h +2
-0@@ -384,6 +384,7 @@ struct kvm_vcpu_arch {u64 last_steal;gpa_t base; } steal; +bool has_reset_once; };/* Pointer to the vcpu's SVE FFR for sve_{save,load}_state() */ @@ -449,6 +450,7 @@ struct kvm_vcpu_arch {#define vcpu_has_sve (vcpu) (system_supports_sve() && \ ((vcpu)->arch.flags & KVM_ARM64_GUEST_HAS_SVE)) +#define vcpu_has_reset_once (vcpu) ((vcpu)->arch.has_reset_once)#ifdef CONFIG_ARM64_PTR_AUTH #define vcpu_has_ptrauth (vcpu) \arch/arm64/kvm/reset.c +4
-0@@ -305,6 +305,10 @@ int kvm_reset_vcpu(struct kvm_vcpu *vcpu)if (loaded)kvm_arch_vcpu_load (vcpu,smp_processor_id ());preempt_enable (); + +if (!ret && !vcpu->arch.has_reset_once) + vcpu->arch.has_reset_once = true; +return ret; }Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 2/28 KVM: arm64: Save ID registers' sanitized value per vCPU
In reply to Reiji WatanabeExtend sys_regs[] of kvm_cpu_context for ID registers and save ID registers' sanitized value in the array for the vCPU at the first vCPU reset. Use the saved ones when ID registers are read by userspace (via KVM_GET_ONE_REG) or the guest.
--- arch/arm64/include/asm/kvm_host.h | 10 ++++++++++ arch/arm64/kvm/sys_regs.c | 24 ++++++++++++++++-------- 2 files changed, 26 insertions(+), 8 deletions(-)
arch/arm64/include/asm/kvm_host.h +10 -0
@@ -145,6 +145,14 @@ struct kvm_vcpu_fault_info {u64 disr_el1;/* Deferred [SError] Status Register */ }; +/* +* (Op0, Op1, CRn, CRm, Op2) of ID registers is (3, 0, 0, crm, op2), +* where 0<=crm<8, 0<=op2<8. +*/ +#define KVM_ARM_ID_REG_MAX_NUM 64 +#define IDREG_IDX (id) ((sys_reg_CRm(id) << 3) | sys_reg_Op2(id)) +#define IDREG_SYS_IDX (id) (ID_REG_BASE + IDREG_IDX(id)) +enum vcpu_sysreg { __INVALID_SYSREG__,/* 0 is reserved as an invalid value */ MPIDR_EL1 ,/* MultiProcessor Affinity Register */
@@ -209,6 +217,8 @@ enum vcpu_sysreg {CNTP_CVAL_EL0 ,CNTP_CTL_EL0 , +ID_REG_BASE , +ID_REG_END =ID_REG_BASE +KVM_ARM_ID_REG_MAX_NUM -1 ,/* Memory Tagging Extension registers */ RGSR_EL1 ,/* Random Allocation Tag Seed Register */ GCR_EL1, /* Tag Control Register */
arch/arm64/kvm/sys_regs.c +16 -8
@@ -273,7 +273,7 @@ static bool trap_loregion(struct kvm_vcpu *vcpu,struct sys_reg_params *p, const struct sys_reg_desc *r) { - u64 val = read_sanitised_ftr_reg(SYS_ID_AA64MMFR1_EL1); + u64 val = __vcpu_sys_reg(vcpu, IDREG_SYS_IDX(SYS_ID_AA64MMFR1_EL1));u32 sr =reg_to_encoding (r);if (!(val & (0xfUL <<ID_AA64MMFR1_LOR_SHIFT ))) {
@@ -1059,12 +1059,11 @@ static bool access_arch_timer(struct kvm_vcpu *vcpu,return true; } -/* Read a sanitised cpufeature ID register by sys_reg_desc */ static u64 read_id_reg (const struct kvm_vcpu *vcpu,struct sys_reg_desc const *r,bool raz) {u32 id =reg_to_encoding (r); -u64 val = raz ?0 :read_sanitised_ftr_reg (id); +u64 val = raz ?0 :__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id));switch (id) {case SYS_ID_AA64PFR0_EL1 :
@@ -1174,6 +1173,16 @@ static unsigned int sve_visibility(const struct kvm_vcpu *vcpu,return REG_HIDDEN ; } +static void reset_id_reg (struct kvm_vcpu *vcpu,const struct sys_reg_desc *rd) +{ +u32 id =reg_to_encoding (rd); + +if (vcpu_has_reset_once (vcpu)) +return ; + +__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id)) =read_sanitised_ftr_reg (id); +} +static int set_id_aa64pfr0_el1 (struct kvm_vcpu *vcpu,const struct sys_reg_desc *rd,const struct kvm_one_reg *reg,void __user *uaddr)
@@ -1219,9 +1228,7 @@ static int set_id_aa64pfr0_el1(struct kvm_vcpu *vcpu,/* * cpufeature ID register user accessors * -* For now, these registers are immutable for userspace, so no values -* are stored, and for set_id_reg() we don't allow the effective value -* to be changed. +* We don't allow the effective value to be changed. */ static int __get_id_reg(const struct kvm_vcpu *vcpu, const struct sys_reg_desc *rd, void __user *uaddr,
@@ -1375,6 +1382,7 @@ static unsigned int mte_visibility(const struct kvm_vcpu *vcpu,#define ID_SANITISED (name) { \ SYS_DESC(SYS_##name), \ .access = access_id_reg, \ + .reset = reset_id_reg, \ .get_user = get_id_reg, \ .set_user = set_id_reg, \ .visibility = id_visibility, \
@@ -1830,8 +1838,8 @@ static bool trap_dbgdidr(struct kvm_vcpu *vcpu,if (p->is_write) {return ignore_write (vcpu, p); }else { -u64 dfr =read_sanitised_ftr_reg (SYS_ID_AA64DFR0_EL1 ); -u64 pfr =read_sanitised_ftr_reg (SYS_ID_AA64PFR0_EL1 ); +u64 dfr =__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (SYS_ID_AA64DFR0_EL1 )); +u64 pfr =__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (SYS_ID_AA64PFR0_EL1 ));u32 el3 = !!cpuid_feature_extract_unsigned_field (pfr,ID_AA64PFR0_EL3_SHIFT ); p->regval = ((((dfr >> ID_AA64DFR0_WRPS_SHIFT) & 0xf) << 28) |
Signature · 1 line
2.33.1.1089.g2158813163f-goog
Re: [RFC PATCH v2 02/28] KVM: arm64: Save ID registers' sanitized value per vCPU
Hi Reiji,
Quoted 4 lines · Reiji Watanabe
Extend sys_regs[] of
kvm_cpu_contextfor ID registers and save ID registers' sanitized value in the array for the vCPU at the first vCPU reset. Use the saved ones when ID registers are read by userspace (viaKVM_GET_ONE_REG) or the guest.
Based on my understanding of the series, it appears that we require the CPU identity to be the same amongst all vCPUs in a VM. Is there any value in keeping a single copy in kvm_arch?
Quoted 111 lines
Signed-off-by Reiji Watanabe <[email protected]>--- arch/arm64/include/asm/kvm_host.h | 10 ++++++++++ arch/arm64/kvm/sys_regs.c | 24 ++++++++++++++++-------- 2 files changed, 26 insertions(+), 8 deletions(-)arch/arm64/include/asm/kvm_host.h +10
-0@@ -145,6 +145,14 @@ struct kvm_vcpu_fault_info {u64 disr_el1;/* Deferred [SError] Status Register */ }; +/* +* (Op0, Op1, CRn, CRm, Op2) of ID registers is (3, 0, 0, crm, op2), +* where 0<=crm<8, 0<=op2<8. +*/ +#define KVM_ARM_ID_REG_MAX_NUM 64 +#define IDREG_IDX (id) ((sys_reg_CRm(id) << 3) | sys_reg_Op2(id)) +#define IDREG_SYS_IDX (id) (ID_REG_BASE + IDREG_IDX(id)) +enum vcpu_sysreg { __INVALID_SYSREG__,/* 0 is reserved as an invalid value */ MPIDR_EL1 ,/* MultiProcessor Affinity Register */ @@ -209,6 +217,8 @@ enum vcpu_sysreg {CNTP_CVAL_EL0 ,CNTP_CTL_EL0 , +ID_REG_BASE , +ID_REG_END =ID_REG_BASE +KVM_ARM_ID_REG_MAX_NUM -1 ,/* Memory Tagging Extension registers */ RGSR_EL1 ,/* Random Allocation Tag Seed Register */ GCR_EL1, /* Tag Control Register */arch/arm64/kvm/sys_regs.c +16
-8@@ -273,7 +273,7 @@ static bool trap_loregion(struct kvm_vcpu *vcpu,struct sys_reg_params *p, const struct sys_reg_desc *r) { - u64 val = read_sanitised_ftr_reg(SYS_ID_AA64MMFR1_EL1); + u64 val = __vcpu_sys_reg(vcpu, IDREG_SYS_IDX(SYS_ID_AA64MMFR1_EL1));u32 sr =reg_to_encoding (r);if (!(val & (0xfUL <<ID_AA64MMFR1_LOR_SHIFT ))) {@@ -1059,12 +1059,11 @@ static bool access_arch_timer(struct kvm_vcpu *vcpu,return true; } -/* Read a sanitised cpufeature ID register by sys_reg_desc */ static u64 read_id_reg (const struct kvm_vcpu *vcpu,struct sys_reg_desc const *r,bool raz) {u32 id =reg_to_encoding (r); -u64 val = raz ?0 :read_sanitised_ftr_reg (id); +u64 val = raz ?0 :__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id));switch (id) {case SYS_ID_AA64PFR0_EL1 :@@ -1174,6 +1173,16 @@ static unsigned int sve_visibility(const struct kvm_vcpu *vcpu,return REG_HIDDEN ; } +static void reset_id_reg (struct kvm_vcpu *vcpu,const struct sys_reg_desc *rd) +{ +u32 id =reg_to_encoding (rd); + +if (vcpu_has_reset_once (vcpu)) +return ; + +__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id)) =read_sanitised_ftr_reg (id); +} +static int set_id_aa64pfr0_el1 (struct kvm_vcpu *vcpu,const struct sys_reg_desc *rd,const struct kvm_one_reg *reg,void __user *uaddr)@@ -1219,9 +1228,7 @@ static int set_id_aa64pfr0_el1(struct kvm_vcpu *vcpu,/* * cpufeature ID register user accessors * -* For now, these registers are immutable for userspace, so no values -* are stored, and for set_id_reg() we don't allow the effective value -* to be changed. +* We don't allow the effective value to be changed. */ static int __get_id_reg(const struct kvm_vcpu *vcpu, const struct sys_reg_desc *rd, void __user *uaddr,@@ -1375,6 +1382,7 @@ static unsigned int mte_visibility(const struct kvm_vcpu *vcpu,#define ID_SANITISED (name) { \ SYS_DESC(SYS_##name), \ .access = access_id_reg, \ + .reset = reset_id_reg, \ .get_user = get_id_reg, \ .set_user = set_id_reg, \ .visibility = id_visibility, \@@ -1830,8 +1838,8 @@ static bool trap_dbgdidr(struct kvm_vcpu *vcpu,if (p->is_write) {return ignore_write (vcpu, p); }else { -u64 dfr =read_sanitised_ftr_reg (SYS_ID_AA64DFR0_EL1 ); -u64 pfr =read_sanitised_ftr_reg (SYS_ID_AA64PFR0_EL1 ); +u64 dfr =__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (SYS_ID_AA64DFR0_EL1 )); +u64 pfr =__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (SYS_ID_AA64PFR0_EL1 ));u32 el3 = !!cpuid_feature_extract_unsigned_field (pfr,ID_AA64PFR0_EL3_SHIFT ); p->regval = ((((dfr >> ID_AA64DFR0_WRPS_SHIFT) & 0xf) << 28) |Signature · 1 line
2.33.1.1089.g2158813163f-goog
Re: [RFC PATCH v2 02/28] KVM: arm64: Save ID registers' sanitized value per vCPU
Hi Oliver,
Quoted 4 lines · Oliver Upton
Hi Reiji,
On Tue, Nov 02, 2021 at 11:24:54PM -0700, Reiji Watanabe wrote:
Quoted 8 lines
Quoted 4 lines
Extend sys_regs[] of
kvm_cpu_contextfor ID registers and save ID registers' sanitized value in the array for the vCPU at the first vCPU reset. Use the saved ones when ID registers are read by userspace (viaKVM_GET_ONE_REG) or the guest.Based on my understanding of the series, it appears that we require the CPU identity to be the same amongst all vCPUs in a VM. Is there any value in keeping a single copy in
kvm_arch?
Yes, that's a good point.
It reminded me that the idea bothered me after we discussed a similar case about your counter offset patches, but I didn't seriously consider that.
Thank you for bringing this up.
I will look into keeping it per VM in kvm_arch.
Regards,
Reiji
Quoted 112 lines
Quoted 112 lines
Signed-off-by Reiji Watanabe <[email protected]>--- arch/arm64/include/asm/kvm_host.h | 10 ++++++++++ arch/arm64/kvm/sys_regs.c | 24 ++++++++++++++++-------- 2 files changed, 26 insertions(+), 8 deletions(-)arch/arm64/include/asm/kvm_host.h +10
-0@@ -145,6 +145,14 @@ struct kvm_vcpu_fault_info {u64 disr_el1;/* Deferred [SError] Status Register */ }; +/* +* (Op0, Op1, CRn, CRm, Op2) of ID registers is (3, 0, 0, crm, op2), +* where 0<=crm<8, 0<=op2<8. +*/ +#define KVM_ARM_ID_REG_MAX_NUM 64 +#define IDREG_IDX (id) ((sys_reg_CRm(id) << 3) | sys_reg_Op2(id)) +#define IDREG_SYS_IDX (id) (ID_REG_BASE + IDREG_IDX(id)) +enum vcpu_sysreg { __INVALID_SYSREG__,/* 0 is reserved as an invalid value */ MPIDR_EL1 ,/* MultiProcessor Affinity Register */ @@ -209,6 +217,8 @@ enum vcpu_sysreg {CNTP_CVAL_EL0 ,CNTP_CTL_EL0 , +ID_REG_BASE , +ID_REG_END =ID_REG_BASE +KVM_ARM_ID_REG_MAX_NUM -1 ,/* Memory Tagging Extension registers */ RGSR_EL1 ,/* Random Allocation Tag Seed Register */ GCR_EL1, /* Tag Control Register */arch/arm64/kvm/sys_regs.c +16
-9@@ -273,7 +273,7 @@ static bool trap_loregion(struct kvm_vcpu *vcpu,struct sys_reg_params *p, const struct sys_reg_desc *r) { - u64 val = read_sanitised_ftr_reg(SYS_ID_AA64MMFR1_EL1); + u64 val = __vcpu_sys_reg(vcpu, IDREG_SYS_IDX(SYS_ID_AA64MMFR1_EL1));u32 sr =reg_to_encoding (r);if (!(val & (0xfUL <<ID_AA64MMFR1_LOR_SHIFT ))) {@@ -1059,12 +1059,11 @@ static bool access_arch_timer(struct kvm_vcpu *vcpu,return true; } -/* Read a sanitised cpufeature ID register by sys_reg_desc */ static u64 read_id_reg (const struct kvm_vcpu *vcpu,struct sys_reg_desc const *r,bool raz) {u32 id =reg_to_encoding (r); -u64 val = raz ?0 :read_sanitised_ftr_reg (id); +u64 val = raz ?0 :__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id));switch (id) {case SYS_ID_AA64PFR0_EL1 :@@ -1174,6 +1173,16 @@ static unsigned int sve_visibility(const struct kvm_vcpu *vcpu,return REG_HIDDEN ; } +static void reset_id_reg (struct kvm_vcpu *vcpu,const struct sys_reg_desc *rd) +{ +u32 id =reg_to_encoding (rd); + +if (vcpu_has_reset_once (vcpu)) +return ; + +__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id)) =read_sanitised_ftr_reg (id); +} +static int set_id_aa64pfr0_el1 (struct kvm_vcpu *vcpu,const struct sys_reg_desc *rd,const struct kvm_one_reg *reg,void __user *uaddr)@@ -1219,9 +1228,7 @@ static int set_id_aa64pfr0_el1(struct kvm_vcpu *vcpu,/* * cpufeature ID register user accessors * -* For now, these registers are immutable for userspace, so no values -* are stored, and for set_id_reg() we don't allow the effective value -* to be changed. +* We don't allow the effective value to be changed. */ static int __get_id_reg(const struct kvm_vcpu *vcpu, const struct sys_reg_desc *rd, void __user *uaddr,@@ -1375,6 +1382,7 @@ static unsigned int mte_visibility(const struct kvm_vcpu *vcpu,#define ID_SANITISED (name) { \ SYS_DESC(SYS_##name), \ .access = access_id_reg, \ + .reset = reset_id_reg, \ .get_user = get_id_reg, \ .set_user = set_id_reg, \ .visibility = id_visibility, \@@ -1830,8 +1838,8 @@ static bool trap_dbgdidr(struct kvm_vcpu *vcpu,if (p->is_write) {return ignore_write (vcpu, p); }else { -u64 dfr =read_sanitised_ftr_reg (SYS_ID_AA64DFR0_EL1 ); -u64 pfr =read_sanitised_ftr_reg (SYS_ID_AA64PFR0_EL1 ); +u64 dfr =__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (SYS_ID_AA64DFR0_EL1 )); +u64 pfr =__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (SYS_ID_AA64PFR0_EL1 ));u32 el3 = !!cpuid_feature_extract_unsigned_field (pfr,ID_AA64PFR0_EL3_SHIFT ); p->regval = ((((dfr >> ID_AA64DFR0_WRPS_SHIFT) & 0xf) << 28) | --2.33.1.1089.g2158813163f-goog
Re: [RFC PATCH v2 02/28] KVM: arm64: Save ID registers' sanitized value per vCPU
Quoted 13 lines · Reiji Watanabe
Hi Oliver,
Quoted 9 lines · Oliver Upton
Hi Reiji,
Quoted 4 lines · Reiji Watanabe
Extend sys_regs[] of
kvm_cpu_contextfor ID registers and save ID registers' sanitized value in the array for the vCPU at the first vCPU reset. Use the saved ones when ID registers are read by userspace (viaKVM_GET_ONE_REG) or the guest.
Quoted 8 lines
Quoted 3 lines
Based on my understanding of the series, it appears that we require the CPU identity to be the same amongst all vCPUs in a VM. Is there any value in keeping a single copy in
kvm_arch?Yes, that's a good point.
It reminded me that the idea bothered me after we discussed a similar case about your counter offset patches, but I didn't seriously consider that.
Yeah, it was a good suggestion for the counter offsetting series, and one that I plan to adopt once I get back to that set :)
--
Thanks,
Oliver
Re: [RFC PATCH v2 02/28] KVM: arm64: Save ID registers' sanitized value per vCPU
In reply to Reiji WatanabeQuoted 17 lines · Reiji Watanabe
Hi Oliver,
Quoted 4 lines · Oliver Upton
Hi Reiji,
On Tue, Nov 02, 2021 at 11:24:54PM -0700, Reiji Watanabe wrote:
Quoted 8 lines
Quoted 4 lines
Extend sys_regs[] of
kvm_cpu_contextfor ID registers and save ID registers' sanitized value in the array for the vCPU at the first vCPU reset. Use the saved ones when ID registers are read by userspace (viaKVM_GET_ONE_REG) or the guest.Based on my understanding of the series, it appears that we require the CPU identity to be the same amongst all vCPUs in a VM. Is there any value in keeping a single copy in
kvm_arch?
Quoted 7 lines
Yes, that's a good point.
It reminded me that the idea bothered me after we discussed a similar case about your counter offset patches, but I didn't seriously consider that.Thank you for bringing this up.
I will look into keeping it per VM inkvm_arch.
I just remembered that I made the prototype that kept ID registers per VM as the option B (, which introduced per VM ID register configuration API though...).
Anyway, I've noticed that requiring the consistency of ID registers amongst vCPUs in a VM affects KVM_ARM_VCPU_INIT API, with which userspace can currently configure different features for each vCPUs. I'm not sure if any existing userspace program practically does that though.
Now, I think I should rather remove that consistency requirement... (at least for features that can be configured by KVM_ARM_VCPU_INIT)
Thanks,
Reiji
RFC PATCH v2 3/28 KVM: arm64: Introduce struct id_reg_info
In reply to Reiji WatanabeThis patch lays the groundwork to make ID registers writable.
Introduce struct id_reg_info for an ID register to manage the register specific control of its value for the guest, and provide set of functions commonly used for ID registers to make them writable.
The id_reg_info is used to do register specific initialization, validation of the ID register and etc. Not all ID registers must have the id_reg_info. ID registers that don't have the id_reg_info are handled in a common way that is applied to all ID registers.
At present, changing an ID register from userspace is allowed only if the ID register has the id_reg_info, but that will be changed by the following patches.
No ID register has the structure yet and the following patches will add the id_reg_info for some ID registers.
--- arch/arm64/include/asm/sysreg.h | 1 + arch/arm64/kvm/sys_regs.c | 222 ++++++++++++++++++++++++++++++-- 2 files changed, 214 insertions(+), 9 deletions(-)
arch/arm64/include/asm/sysreg.h +1 -0
@@ -1186,6 +1186,7 @@#define ICH_VTR_A3V_MASK (1 << ICH_VTR_A3V_SHIFT)#define ARM64_FEATURE_FIELD_BITS 4 +#define ARM64_FEATURE_FIELD_MASK ((1ull << ARM64_FEATURE_FIELD_BITS) - 1)/* Create a mask for the feature bits of the specified feature. */ #define ARM64_FEATURE_MASK (x) (GENMASK_ULL(x##_SHIFT + ARM64_FEATURE_FIELD_BITS - 1, x##_SHIFT))
arch/arm64/kvm/sys_regs.c +213 -9
272 lines not on this page · raw message
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 4/28 KVM: arm64: Keep consistency of ID registers between vCPUs
In reply to Reiji WatanabeAll vCPUs that are owned by a VM must have the same values of ID registers.
Return an error at the very first KVM_RUN for a vCPU if the vCPU has different values in any ID registers from any other vCPUs that have already started KVM_RUN once. Also, return an error if userspace tries to change a value of ID register for a vCPU that already started KVM_RUN once.
Changing ID register is still not allowed at present though.
--- arch/arm64/include/asm/kvm_host.h | 2 ++ arch/arm64/kvm/arm.c | 4 ++++ arch/arm64/kvm/sys_regs.c | 31 +++++++++++++++++++++++++++++++ 3 files changed, 37 insertions(+)
arch/arm64/include/asm/kvm_host.h +2 -0
@@ -745,6 +745,8 @@ int kvm_arm_vcpu_arch_has_attr(struct kvm_vcpu *vcpu,long kvm_vm_ioctl_mte_copy_tags (struct kvm *kvm,struct kvm_arm_copy_mte_tags *copy_tags); +int kvm_id_regs_consistency_check (const struct kvm_vcpu *vcpu); +/* Guest/host FPSIMD coordination helpers */ int kvm_arch_vcpu_run_map_fp (struct kvm_vcpu *vcpu);void kvm_arch_vcpu_load_fp (struct kvm_vcpu *vcpu);
arch/arm64/kvm/arm.c +4 -0
@@ -595,6 +595,10 @@ static int kvm_vcpu_first_run_init(struct kvm_vcpu *vcpu)return -EPERM ; vcpu->arch.has_run_once = true; +if (kvm_id_regs_consistency_check (vcpu)) { + vcpu->arch.has_run_once = false; +return -EPERM ; + }kvm_arm_vcpu_init_debug (vcpu);
arch/arm64/kvm/sys_regs.c +31 -0
@@ -1436,6 +1436,10 @@ static int __set_id_reg(struct kvm_vcpu *vcpu,if (val !=read_id_reg (vcpu, rd, raz) && !GET_ID_REG_INFO (encoding))return -EINVAL ; +/* Don't allow to change the reg after the first KVM_RUN. */ +if (vcpu->arch.has_run_once) +return -EINVAL ; +if (raz)return 0 ;
@@ -3004,6 +3008,33 @@ int kvm_arm_copy_sys_reg_indices(struct kvm_vcpu *vcpu, u64 __user *uindices)return write_demux_regids (uindices); } +int kvm_id_regs_consistency_check (const struct kvm_vcpu *vcpu) +{ +int i; +const struct kvm_vcpu *t_vcpu; + +/* +* Make sure vcpu->arch.has_run_once is visible for others so that +* ID regs' consistency between two vCPUs is checked by either one +* at least. +*/ +smp_mb (); +WARN_ON (!vcpu->arch.has_run_once); + +kvm_for_each_vcpu (i, t_vcpu, vcpu->kvm) { +if (!t_vcpu->arch.has_run_once) +/* ID regs still could be updated. */ +continue ; + +if (memcmp (&__vcpu_sys_reg (vcpu,ID_REG_BASE ), + &__vcpu_sys_reg (t_vcpu,ID_REG_BASE ), +sizeof (__vcpu_sys_reg (vcpu,ID_REG_BASE )) * +KVM_ARM_ID_REG_MAX_NUM )) +return -EINVAL ; + } +return 0 ; +} +static void id_reg_info_init_all (void ) {int i;
Signature · 1 line
2.33.1.1089.g2158813163f-goog
Re: [RFC PATCH v2 04/28] KVM: arm64: Keep consistency of ID registers between vCPUs
Quoted 36 lines · Reiji Watanabe
All vCPUs that are owned by a VM must have the same values of ID registers.
Return an error at the very first
KVM_RUNfor a vCPU if the vCPU has different values in any ID registers from any other vCPUs that have already startedKVM_RUNonce. Also, return an error if userspace tries to change a value of ID register for a vCPU that already startedKVM_RUNonce.Changing ID register is still not allowed at present though.
Signed-off-by Reiji Watanabe <[email protected]>--- arch/arm64/include/asm/kvm_host.h | 2 ++ arch/arm64/kvm/arm.c | 4 ++++ arch/arm64/kvm/sys_regs.c | 31 +++++++++++++++++++++++++++++++ 3 files changed, 37 insertions(+)arch/arm64/include/asm/kvm_host.h +2
-0@@ -745,6 +745,8 @@ int kvm_arm_vcpu_arch_has_attr(struct kvm_vcpu *vcpu,long kvm_vm_ioctl_mte_copy_tags (struct kvm *kvm,struct kvm_arm_copy_mte_tags *copy_tags); +int kvm_id_regs_consistency_check (const struct kvm_vcpu *vcpu); +/* Guest/host FPSIMD coordination helpers */ int kvm_arch_vcpu_run_map_fp (struct kvm_vcpu *vcpu);void kvm_arch_vcpu_load_fp (struct kvm_vcpu *vcpu);arch/arm64/kvm/arm.c +0
-0
arch/arm64/kvm/arm.c static int kvm_vcpu_first_run_init(struct kvm_vcpu *vcpu) · line 601
Quoted 7 lines
arch/arm64/kvm/arm.c +4
-0@@ -595,6 +595,10 @@ static int kvm_vcpu_first_run_init(struct kvm_vcpu *vcpu)return -EPERM ; vcpu->arch.has_run_once = true; +if (kvm_id_regs_consistency_check (vcpu)) { + vcpu->arch.has_run_once = false; +return -EPERM ; + }
It might be nice to return an error to userspace synchronously (i.e. on the register write). Of course, there is still the issue where userspace writes to some (but not all) of the vCPU feature ID registers, which can't be known until the first KVM_RUN.
Quoted 39 lines
arch/arm64/kvm/arm.c +0
-0kvm_arm_vcpu_init_debug (vcpu);arch/arm64/kvm/sys_regs.c +21
-0@@ -1436,6 +1436,10 @@ static int __set_id_reg(struct kvm_vcpu *vcpu,if (val !=read_id_reg (vcpu, rd, raz) && !GET_ID_REG_INFO (encoding))return -EINVAL ; +/* Don't allow to change the reg after the first KVM_RUN. */ +if (vcpu->arch.has_run_once) +return -EINVAL ; +if (raz)return 0 ;@@ -3004,6 +3008,33 @@ int kvm_arm_copy_sys_reg_indices(struct kvm_vcpu *vcpu, u64 __user *uindices)return write_demux_regids (uindices); } +int kvm_id_regs_consistency_check (const struct kvm_vcpu *vcpu) +{ +int i; +const struct kvm_vcpu *t_vcpu; + +/* +* Make sure vcpu->arch.has_run_once is visible for others so that +* ID regs' consistency between two vCPUs is checked by either one +* at least. +*/ +smp_mb (); +WARN_ON (!vcpu->arch.has_run_once); + +kvm_for_each_vcpu (i, t_vcpu, vcpu->kvm) { +if (!t_vcpu->arch.has_run_once) +/* ID regs still could be updated. */ +continue ;
arch/arm64/kvm/sys_regs.c int kvm_arm_copy_sys_reg_indices(struct kvm_vcpu *vcpu, u64 __user *uindices) · line 3037
Quoted 10 lines
arch/arm64/kvm/sys_regs.c +10
-0+ +if (memcmp (&__vcpu_sys_reg (vcpu,ID_REG_BASE ), + &__vcpu_sys_reg (t_vcpu,ID_REG_BASE ), +sizeof (__vcpu_sys_reg (vcpu,ID_REG_BASE )) * +KVM_ARM_ID_REG_MAX_NUM )) +return -EINVAL ; + } +return 0 ; +} +
Couldn't we do the consistency check exactly once per VM? I had alluded to this when reviewing Raghu's patches, but I think the same applies here too: an abstraction for detecting the first vCPU to run in a VM.
https://lore.kernel.org/all/[email protected]/
--
Thanks
Oliver
Re: [RFC PATCH v2 04/28] KVM: arm64: Keep consistency of ID registers between vCPUs
Hi Oliver,
Quoted 40 lines · Oliver Upton
Quoted 38 lines · Reiji Watanabe
All vCPUs that are owned by a VM must have the same values of ID registers.
Return an error at the very first
KVM_RUNfor a vCPU if the vCPU has different values in any ID registers from any other vCPUs that have already startedKVM_RUNonce. Also, return an error if userspace tries to change a value of ID register for a vCPU that already startedKVM_RUNonce.Changing ID register is still not allowed at present though.
Signed-off-by Reiji Watanabe <[email protected]>--- arch/arm64/include/asm/kvm_host.h | 2 ++ arch/arm64/kvm/arm.c | 4 ++++ arch/arm64/kvm/sys_regs.c | 31 +++++++++++++++++++++++++++++++ 3 files changed, 37 insertions(+)arch/arm64/include/asm/kvm_host.h +2
-0@@ -745,6 +745,8 @@ int kvm_arm_vcpu_arch_has_attr(struct kvm_vcpu *vcpu,long kvm_vm_ioctl_mte_copy_tags (struct kvm *kvm,struct kvm_arm_copy_mte_tags *copy_tags); +int kvm_id_regs_consistency_check (const struct kvm_vcpu *vcpu); +/* Guest/host FPSIMD coordination helpers */ int kvm_arch_vcpu_run_map_fp (struct kvm_vcpu *vcpu);void kvm_arch_vcpu_load_fp (struct kvm_vcpu *vcpu);arch/arm64/kvm/arm.c +0
-0@@ -595,6 +595,10 @@ static int kvm_vcpu_first_run_init(struct kvm_vcpu *vcpu)return -EPERM ;
Quoted 10 lines
arch/arm64/kvm/arm.c static int kvm_vcpu_first_run_init(struct kvm_vcpu *vcpu) · line 601
Quoted 5 lines
arch/arm64/kvm/arm.c +4
-0vcpu->arch.has_run_once = true; +if (kvm_id_regs_consistency_check (vcpu)) { + vcpu->arch.has_run_once = false; +return -EPERM ; + }It might be nice to return an error to userspace synchronously (i.e. on the register write). Of course, there is still the issue where userspace writes to some (but not all) of the vCPU feature ID registers, which can't be known until the first
KVM_RUN.
Yes, I agree that it would be better. As I mentioned for patch-02, I will remove the consistency checking amongst vCPUs anyway though.
Quoted 53 lines
Quoted 38 lines
arch/arm64/kvm/arm.c +0
-0kvm_arm_vcpu_init_debug (vcpu);arch/arm64/kvm/sys_regs.c +21
-0@@ -1436,6 +1436,10 @@ static int __set_id_reg(struct kvm_vcpu *vcpu,if (val !=read_id_reg (vcpu, rd, raz) && !GET_ID_REG_INFO (encoding))return -EINVAL ; +/* Don't allow to change the reg after the first KVM_RUN. */ +if (vcpu->arch.has_run_once) +return -EINVAL ; +if (raz)return 0 ;@@ -3004,6 +3008,33 @@ int kvm_arm_copy_sys_reg_indices(struct kvm_vcpu *vcpu, u64 __user *uindices)return write_demux_regids (uindices); } +int kvm_id_regs_consistency_check (const struct kvm_vcpu *vcpu) +{ +int i; +const struct kvm_vcpu *t_vcpu; + +/* +* Make sure vcpu->arch.has_run_once is visible for others so that +* ID regs' consistency between two vCPUs is checked by either one +* at least. +*/ +smp_mb (); +WARN_ON (!vcpu->arch.has_run_once); + +kvm_for_each_vcpu (i, t_vcpu, vcpu->kvm) { +if (!t_vcpu->arch.has_run_once) +/* ID regs still could be updated. */ +continue ;arch/arm64/kvm/sys_regs.c int kvm_arm_copy_sys_reg_indices(struct kvm_vcpu *vcpu, u64 __user *uindices) · line 3037
Quoted 10 lines
arch/arm64/kvm/sys_regs.c +10
-0+ +if (memcmp (&__vcpu_sys_reg (vcpu,ID_REG_BASE ), + &__vcpu_sys_reg (t_vcpu,ID_REG_BASE ), +sizeof (__vcpu_sys_reg (vcpu,ID_REG_BASE )) * +KVM_ARM_ID_REG_MAX_NUM )) +return -EINVAL ; + } +return 0 ; +} +Couldn't we do the consistency check exactly once per VM? I had alluded to this when reviewing Raghu's patches, but I think the same applies here too: an abstraction for detecting the first vCPU to run in a VM.
Quoted 1 line
Yes, the same applies to this, as well.
Thank you so much for your review !
Regards,
Reiji
RFC PATCH v2 5/28 KVM: arm64: Make ID_AA64PFR0_EL1 writable
In reply to Reiji WatanabeThis patch adds id_reg_info for ID_AA64PFR0_EL1 to make it writable by userspace.
The CSV2/CSV3 fields of the register were already writable and values that were written for them affected all vCPUs before. Now they only affect the vCPU.
Return an error if userspace tries to set SVE field of the register to a value that conflicts with SVE configuration for the guest (via KVM_ARM_VCPU_INIT). SIMD/FP/SVE fields of the requested value are validated according to Arm ARM.
--- arch/arm64/include/asm/kvm_host.h | 3 - arch/arm64/kvm/arm.c | 18 ----- arch/arm64/kvm/sys_regs.c | 122 +++++++++++++++++------------- 3 files changed, 68 insertions(+), 75 deletions(-)
arch/arm64/include/asm/kvm_host.h +0 -3
@@ -131,9 +131,6 @@ struct kvm_arch {unsigned long *pmu_filter;unsigned int pmuver; -u8 pfr0_csv2; -u8 pfr0_csv3; -/* Memory Tagging Extension enabled for the guest */ bool mte_enabled; };
arch/arm64/kvm/arm.c +0 -18
@@ -114,22 +114,6 @@ static int kvm_arm_default_max_vcpus(void)return vgic_present ?kvm_vgic_get_max_vcpus () :KVM_MAX_VCPUS ; } -static void set_default_spectre (struct kvm *kvm) -{ -/* -* The default is to expose CSV2 == 1 if the HW isn't affected. -* Although this is a per-CPU feature, we make it global because -* asymmetric systems are just a nuisance. -* -* Userspace can override this as long as it doesn't promise -* the impossible. -*/ -if (arm64_get_spectre_v2_state () ==SPECTRE_UNAFFECTED ) - kvm->arch.pfr0_csv2 =1 ; -if (arm64_get_meltdown_state () ==SPECTRE_UNAFFECTED ) - kvm->arch.pfr0_csv3 =1 ; -} -/** * kvm_arch_init_vm - initializes a VM data structure * @kvm: pointer to the KVM struct
@@ -155,8 +139,6 @@ int kvm_arch_init_vm(struct kvm *kvm, unsigned long type)/* The maximum number of VCPUs is limited by the host's GIC model */ kvm->arch.max_vcpus =kvm_arm_default_max_vcpus (); -set_default_spectre (kvm); -return ret; out_free_stage2_pgd:kvm_free_stage2_pgd (&kvm->arch.mmu);
arch/arm64/kvm/sys_regs.c +68 -54
152 lines not on this page · raw message
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 6/28 KVM: arm64: Make ID_AA64PFR1_EL1 writable
In reply to Reiji WatanabeThis patch adds id_reg_info for ID_AA64PFR1_EL1 to make it writable by userspace.
Return an error if userspace tries to set MTE field of the register to a value that conflicts with KVM_CAP_ARM_MTE configuration for the guest.
Skip fractional feature fields validation at present and they will be handled by the following patches.
--- arch/arm64/include/asm/sysreg.h | 1 + arch/arm64/kvm/sys_regs.c | 50 ++++++++++++++++++++++++++------- 2 files changed, 41 insertions(+), 10 deletions(-)
arch/arm64/include/asm/sysreg.h +1 -0
@@ -793,6 +793,7 @@#define ID_AA64PFR0_ELx_32BIT_64BIT 0x2/* id_aa64pfr1 */ +#define ID_AA64PFR1_CSV2FRAC_SHIFT 32#define ID_AA64PFR1_MPAMFRAC_SHIFT 16#define ID_AA64PFR1_RASFRAC_SHIFT 12#define ID_AA64PFR1_MTE_SHIFT 8
arch/arm64/kvm/sys_regs.c +40 -10
86 lines not on this page · raw message
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 7/28 KVM: arm64: Make ID_AA64ISAR0_EL1 writable
In reply to Reiji WatanabeThis patch adds id_reg_info for ID_AA64ISAR0_EL1 to make it writable by userspace.
Updating sm3, sm4, sha1, sha2 and sha3 fields are allowed only if values of those fields follow Arm ARM.
--- arch/arm64/kvm/sys_regs.c | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+)
arch/arm64/kvm/sys_regs.c +29 -0
@@ -437,6 +437,29 @@ static int validate_id_aa64pfr1_el1(struct kvm_vcpu *vcpu,return 0 ; } +static int validate_id_aa64isar0_el1 (struct kvm_vcpu *vcpu, +const struct id_reg_info *id_reg,u64 val) +{ +unsigned int sm3, sm4, sha1, sha2, sha3; + +/* Run consistency checkings according to Arm ARM */ + sm3 =cpuid_feature_extract_unsigned_field (val,ID_AA64ISAR0_SM3_SHIFT ); + sm4 =cpuid_feature_extract_unsigned_field (val,ID_AA64ISAR0_SM4_SHIFT ); +if (sm3 != sm4) +return -EINVAL ; + + sha1 =cpuid_feature_extract_unsigned_field (val,ID_AA64ISAR0_SHA1_SHIFT ); + sha2 =cpuid_feature_extract_unsigned_field (val,ID_AA64ISAR0_SHA2_SHIFT ); +if ((sha1 ==0 ) ^ (sha2 ==0 )) +return -EINVAL ; + + sha3 =cpuid_feature_extract_unsigned_field (val,ID_AA64ISAR0_SHA3_SHIFT ); +if (((sha2 ==2 ) ^ (sha3 ==1 )) || (!sha1 && sha3)) +return -EINVAL ; + +return 0 ; +} +static void init_id_aa64pfr0_el1_info (struct id_reg_info *id_reg) {u64 limit = id_reg->vcpu_limit_val;
@@ -502,6 +525,11 @@ static struct id_reg_info id_aa64pfr1_el1_info = { .get_reset_val = get_reset_id_aa64pfr1_el1, }; +static struct id_reg_info id_aa64isar0_el1_info = { + .sys_reg =SYS_ID_AA64ISAR0_EL1 , + .validate = validate_id_aa64isar0_el1, +}; +/* * An ID register that needs special handling to control the value for the * guest must have its own id_reg_info in id_reg_info_table.
@@ -513,6 +541,7 @@ static struct id_reg_info id_aa64pfr1_el1_info = {static struct id_reg_info *id_reg_info_table[KVM_ARM_ID_REG_MAX_NUM ] = { [IDREG_IDX (SYS_ID_AA64PFR0_EL1 )] = &id_aa64pfr0_el1_info, [IDREG_IDX (SYS_ID_AA64PFR1_EL1 )] = &id_aa64pfr1_el1_info, + [IDREG_IDX (SYS_ID_AA64ISAR0_EL1 )] = &id_aa64isar0_el1_info, }; static int validate_id_reg(struct kvm_vcpu *vcpu,
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 8/28 KVM: arm64: Make ID_AA64ISAR1_EL1 writable
In reply to Reiji WatanabeThis patch adds id_reg_info for ID_AA64ISAR1_EL1 to make it writable by userspace.
Return an error if userspace tries to set PTRAUTH related fields of the register to values that conflict with PTRAUTH configuration, which was configured by KVM_ARM_VCPU_INIT, for the guest.
--- arch/arm64/kvm/sys_regs.c | 79 +++++++++++++++++++++++++++++++++++---- 1 file changed, 72 insertions(+), 7 deletions(-)
arch/arm64/kvm/sys_regs.c +72 -7
@@ -356,6 +356,24 @@ static int arm64_check_features(u64 check_types, u64 val, u64 lim)return 0 ; } +#define PTRAUTH_MASK (ARM64_FEATURE_MASK(ID_AA64ISAR1_APA) | \ + ARM64_FEATURE_MASK(ID_AA64ISAR1_API) | \ + ARM64_FEATURE_MASK(ID_AA64ISAR1_GPA) | \ + ARM64_FEATURE_MASK(ID_AA64ISAR1_GPI)) + +#define aa64isar1_has_apa (val) \ + (cpuid_feature_extract_unsigned_field(val, ID_AA64ISAR1_APA_SHIFT) >= \ + ID_AA64ISAR1_APA_ARCHITECTED) +#define aa64isar1_has_api (val) \ + (cpuid_feature_extract_unsigned_field(val, ID_AA64ISAR1_API_SHIFT) >= \ + ID_AA64ISAR1_API_IMP_DEF) +#define aa64isar1_has_gpa (val) \ + (cpuid_feature_extract_unsigned_field(val, ID_AA64ISAR1_GPA_SHIFT) >= \ + ID_AA64ISAR1_GPA_ARCHITECTED) +#define aa64isar1_has_gpi (val) \ + (cpuid_feature_extract_unsigned_field(val, ID_AA64ISAR1_GPI_SHIFT) >= \ + ID_AA64ISAR1_GPI_IMP_DEF) +struct id_reg_info {u32 sys_reg;/* Register ID */
@@ -460,6 +478,36 @@ static int validate_id_aa64isar0_el1(struct kvm_vcpu *vcpu,return 0 ; } +static int validate_id_aa64isar1_el1 (struct kvm_vcpu *vcpu, +const struct id_reg_info *id_reg,u64 val) +{ +bool has_gpi, has_gpa, has_api, has_apa; +bool generic, address; + + has_gpi =aa64isar1_has_gpi (val); + has_gpa =aa64isar1_has_gpa (val); + has_api =aa64isar1_has_api (val); + has_apa =aa64isar1_has_apa (val); +if ((has_gpi && has_gpa) || (has_api && has_apa)) +return -EINVAL ; + + generic = has_gpi || has_gpa; + address = has_api || has_apa; +/* +* Since the current KVM guest implementation works by enabling +* both address/generic pointer authentication features, +* return an error if they conflict. +*/ +if (generic ^ address) +return -EPERM ; + +/* Check if there is a conflict with a request via KVM_ARM_VCPU_INIT */ +if (vcpu_has_ptrauth (vcpu) ^ (generic && address)) +return -EPERM ; + +return 0 ; +} +static void init_id_aa64pfr0_el1_info (struct id_reg_info *id_reg) {u64 limit = id_reg->vcpu_limit_val;
@@ -490,6 +538,12 @@ static void init_id_aa64pfr1_el1_info(struct id_reg_info *id_reg) id_reg->vcpu_limit_val &= ~ARM64_FEATURE_MASK (ID_AA64PFR1_MTE ); } +static void init_id_aa64isar1_el1_info (struct id_reg_info *id_reg) +{ +if (!system_has_full_ptr_auth ()) + id_reg->vcpu_limit_val &= ~PTRAUTH_MASK ; +} +static u64 get_reset_id_aa64pfr0_el1 (struct kvm_vcpu *vcpu,const struct id_reg_info *idr) {
@@ -506,6 +560,13 @@ static u64 get_reset_id_aa64pfr1_el1(struct kvm_vcpu *vcpu, (idr->vcpu_limit_val & ~(ARM64_FEATURE_MASK (ID_AA64PFR1_MTE ))); } +static u64 get_reset_id_aa64isar1_el1 (struct kvm_vcpu *vcpu, +const struct id_reg_info *idr) +{ +return vcpu_has_ptrauth (vcpu) ? + idr->vcpu_limit_val : (idr->vcpu_limit_val & ~PTRAUTH_MASK ); +} +static struct id_reg_info id_aa64pfr0_el1_info = { .sys_reg =SYS_ID_AA64PFR0_EL1 , .ftr_check_types = S_FCT(ID_AA64PFR0_ASIMD_SHIFT, FCT_LOWER_SAFE) |
@@ -530,6 +591,16 @@ static struct id_reg_info id_aa64isar0_el1_info = { .validate = validate_id_aa64isar0_el1, }; +static struct id_reg_info id_aa64isar1_el1_info = { + .sys_reg =SYS_ID_AA64ISAR1_EL1 , + .ftr_check_types = +U_FCT (ID_AA64ISAR1_API_SHIFT ,FCT_EXACT_OR_ZERO_SAFE ) | +U_FCT (ID_AA64ISAR1_APA_SHIFT ,FCT_EXACT_OR_ZERO_SAFE ), + .init = init_id_aa64isar1_el1_info, + .validate = validate_id_aa64isar1_el1, + .get_reset_val = get_reset_id_aa64isar1_el1, +}; +/* * An ID register that needs special handling to control the value for the * guest must have its own id_reg_info in id_reg_info_table.
@@ -542,6 +613,7 @@ static struct id_reg_info *id_reg_info_table[KVM_ARM_ID_REG_MAX_NUM] = { [IDREG_IDX(SYS_ID_AA64PFR0_EL1)] = &id_aa64pfr0_el1_info, [IDREG_IDX(SYS_ID_AA64PFR1_EL1)] = &id_aa64pfr1_el1_info, [IDREG_IDX(SYS_ID_AA64ISAR0_EL1)] = &id_aa64isar0_el1_info, + [IDREG_IDX(SYS_ID_AA64ISAR1_EL1)] = &id_aa64isar1_el1_info, }; static int validate_id_reg(struct kvm_vcpu *vcpu,
@@ -1376,13 +1448,6 @@ static u64 read_id_reg(const struct kvm_vcpu *vcpu,u64 val = raz ?0 :__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id));switch (id) { -case SYS_ID_AA64ISAR1_EL1 : -if (!vcpu_has_ptrauth (vcpu)) - val &= ~(ARM64_FEATURE_MASK (ID_AA64ISAR1_APA ) | -ARM64_FEATURE_MASK (ID_AA64ISAR1_API ) | -ARM64_FEATURE_MASK (ID_AA64ISAR1_GPA ) | -ARM64_FEATURE_MASK (ID_AA64ISAR1_GPI )); -break ;case SYS_ID_AA64DFR0_EL1 :/* Limit debug to ARMv8.0 */ val &= ~ARM64_FEATURE_MASK (ID_AA64DFR0_DEBUGVER );
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 9/28 KVM: arm64: Make ID_AA64MMFR0_EL1 writable
In reply to Reiji WatanabeThis patch adds id_reg_info for ID_AA64MMFR0_EL1 to make it writable by userspace.
Since ID_AA64MMFR0_EL1 stage 2 granule size fields don't follow the standard ID scheme, we need a special handling to validate those fields.
--- arch/arm64/kvm/sys_regs.c | 118 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 118 insertions(+)
arch/arm64/kvm/sys_regs.c +118 -0
@@ -508,6 +508,113 @@ static int validate_id_aa64isar1_el1(struct kvm_vcpu *vcpu,return 0 ; } +/* +* Check if the requested stage2 translation granule size indicated in +* @mmfr0 is also indicated in @mmfr0_lim. This function assumes that +* the stage1 granule size indicated in @mmfr0 has been validated already. +*/ +static int aa64mmfr0_tgran2_check (int field,u64 mmfr0,u64 mmfr0_lim) +{ +s64 tgran2, lim_tgran2, rtgran1; +int f1; +bool is_signed = true; + + tgran2 =cpuid_feature_extract_unsigned_field (mmfr0, field); + lim_tgran2 =cpuid_feature_extract_unsigned_field (mmfr0_lim, field); +if (tgran2 == lim_tgran2) +return 0 ; + +if (tgran2 && lim_tgran2) +return (tgran2 > lim_tgran2) ? -E2BIG :0 ; + +/* +* Either tgran2 or lim_tgran2 is zero. +* Need stage1 granule size to validate tgran2. +*/ +switch (field) { +case ID_AA64MMFR0_TGRAN4_2_SHIFT : + f1 =ID_AA64MMFR0_TGRAN4_SHIFT ; +break ; +case ID_AA64MMFR0_TGRAN64_2_SHIFT : + f1 =ID_AA64MMFR0_TGRAN64_SHIFT ; +break ; +case ID_AA64MMFR0_TGRAN16_2_SHIFT : + f1 =ID_AA64MMFR0_TGRAN16_SHIFT ; + is_signed = false; +break ; +default : +/* Should never happen */ +WARN_ONCE (1 ,"Unexpected stage2 granule field (%d)\n" , field); +return 0 ; + } + +/* +* If tgran2 == 0 (&& lim_tgran2 != 0), the requested stage2 granule +* size is indicated in the stage1 granule size field of @mmfr0. +* So, validate the stage1 granule size against the stage2 limit +* granule size. +* If lim_tgran2 == 0 (&& tgran2 != 0), the stage2 limit granule size +* is indicated in the stage1 granule size field of @mmfr0_lim. +* So, validate the requested stage2 granule size against the stage1 +* limit granule size. +*/ + +/* Get the relevant stage1 granule size to validate tgran2 */ +if (tgran2 ==0 ) +/* The requested stage1 granule size */ + rtgran1 =cpuid_feature_extract_field (mmfr0, f1, is_signed); +else /* lim_tgran2 == 0 */ +/* The stage1 limit granule size */ + rtgran1 =cpuid_feature_extract_field (mmfr0_lim, f1, is_signed); + +/* +* Adjust the value of rtgran1 to compare with stage2 granule size, +* which indicates: 1: Not supported, 2: Supported, etc. +*/ +if (is_signed) +/* For signed, -1: Not supported, 0: Supported, etc. */ + rtgran1 +=0x2 ; +else +/* For unsigned, 0: Not supported, 1: Supported, etc. */ + rtgran1 +=0x1 ; + +if ((tgran2 ==0 ) && (rtgran1 > lim_tgran2)) +/* +* The requested stage1 granule size (== the requested stage2 +* granule size) is larger than the stage2 limit granule size. +*/ +return -E2BIG ; +else if ((lim_tgran2 ==0 ) && (tgran2 > rtgran1)) +/* +* The requested stage2 granule size is larger than the stage1 +* limit granulze size (== the stage2 limit granule size). +*/ +return -E2BIG ; + +return 0 ; +} + +static int validate_id_aa64mmfr0_el1 (struct kvm_vcpu *vcpu, +const struct id_reg_info *id_reg,u64 val) +{ +u64 limit = id_reg->vcpu_limit_val; +int ret; + + ret =aa64mmfr0_tgran2_check (ID_AA64MMFR0_TGRAN4_2_SHIFT , val, limit); +if (ret) +return ret; + + ret =aa64mmfr0_tgran2_check (ID_AA64MMFR0_TGRAN64_2_SHIFT , val, limit); +if (ret) +return ret; + + ret =aa64mmfr0_tgran2_check (ID_AA64MMFR0_TGRAN16_2_SHIFT , val, limit); +if (ret) +return ret; + +return 0 ; +} +static void init_id_aa64pfr0_el1_info (struct id_reg_info *id_reg) {u64 limit = id_reg->vcpu_limit_val;
@@ -601,6 +708,16 @@ static struct id_reg_info id_aa64isar1_el1_info = { .get_reset_val = get_reset_id_aa64isar1_el1, }; +static struct id_reg_info id_aa64mmfr0_el1_info = { + .sys_reg =SYS_ID_AA64MMFR0_EL1 , + .ftr_check_types =S_FCT (ID_AA64MMFR0_TGRAN4_SHIFT ,FCT_LOWER_SAFE ) | +S_FCT (ID_AA64MMFR0_TGRAN64_SHIFT ,FCT_LOWER_SAFE ) | +U_FCT (ID_AA64MMFR0_TGRAN4_2_SHIFT ,FCT_IGNORE ) | +U_FCT (ID_AA64MMFR0_TGRAN64_2_SHIFT ,FCT_IGNORE ) | +U_FCT (ID_AA64MMFR0_TGRAN16_2_SHIFT ,FCT_IGNORE ), + .validate = validate_id_aa64mmfr0_el1, +}; +/* * An ID register that needs special handling to control the value for the * guest must have its own id_reg_info in id_reg_info_table.
@@ -614,6 +731,7 @@ static struct id_reg_info *id_reg_info_table[KVM_ARM_ID_REG_MAX_NUM] = { [IDREG_IDX(SYS_ID_AA64PFR1_EL1)] = &id_aa64pfr1_el1_info, [IDREG_IDX(SYS_ID_AA64ISAR0_EL1)] = &id_aa64isar0_el1_info, [IDREG_IDX(SYS_ID_AA64ISAR1_EL1)] = &id_aa64isar1_el1_info, + [IDREG_IDX(SYS_ID_AA64MMFR0_EL1)] = &id_aa64mmfr0_el1_info, }; static int validate_id_reg(struct kvm_vcpu *vcpu,
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 10/28 KVM: arm64: Hide IMPLEMENTATION DEFINED PMU support for the guest
In reply to Reiji WatanabeWhen ID_AA64DFR0_EL1.PMUVER or ID_DFR0_EL1.PERFMON is 0xf, which means IMPLEMENTATION DEFINED PMU supported, KVM unconditionally expose the value for the guest as it is. Since KVM doesn't support IMPLEMENTATION DEFINED PMU for the guest, in that case KVM should exopse 0x0 (PMU is not implemented) instead.
Change cpuid_feature_cap_perfmon_field() to update the field value to 0x0 when it is 0xf.
--- arch/arm64/include/asm/cpufeature.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/include/asm/cpufeature.h +1 -1
@@ -553,7 +553,7 @@ cpuid_feature_cap_perfmon_field(u64 features, int field, u64 cap)/* Treat IMPLEMENTATION DEFINED functionality as unimplemented */ if (val ==ID_AA64DFR0_PMUVER_IMP_DEF ) - val =0 ; +return (features & ~mask);if (val > cap) { features &= ~mask;
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 11/28 KVM: arm64: Make ID_AA64DFR0_EL1 writable
In reply to Reiji WatanabeThis patch adds id_reg_info for ID_AA64DFR0_EL1 to make it writable by userspace.
Return an error if userspace tries to set PMUVER field of the register to a value that conflicts with the PMU configuration.
Since number of context-aware breakpoints must be no more than number of supported breakpoints according to Arm ARM, return an error if userspace tries to set CTX_CMPS field to such value.
--- arch/arm64/kvm/sys_regs.c | 84 ++++++++++++++++++++++++++++++++++----- 1 file changed, 73 insertions(+), 11 deletions(-)
arch/arm64/kvm/sys_regs.c +73 -11
@@ -615,6 +615,45 @@ static int validate_id_aa64mmfr0_el1(struct kvm_vcpu *vcpu,return 0 ; } +static bool id_reg_has_pmu (u64 val,u64 shift,unsigned int min) +{ +unsigned int pmu =cpuid_feature_extract_unsigned_field (val, shift); + +/* +* Treat IMPLEMENTATION DEFINED functionality as unimplemented for +* ID_AA64DFR0_EL1.PMUVer/ID_DFR0_EL1.PerfMon. +*/ +if (pmu ==0xf ) + pmu =0 ; + +return (pmu >= min); +} + +static int validate_id_aa64dfr0_el1 (struct kvm_vcpu *vcpu, +const struct id_reg_info *id_reg,u64 val) +{ +unsigned int brps, ctx_cmps; +bool vcpu_pmu, dfr0_pmu; + + brps =cpuid_feature_extract_unsigned_field (val,ID_AA64DFR0_BRPS_SHIFT ); + ctx_cmps =cpuid_feature_extract_unsigned_field (val,ID_AA64DFR0_CTX_CMPS_SHIFT ); + +/* +* Number of context-aware breakpoints can be no more than number of +* supported breakpoints. +*/ +if (ctx_cmps > brps) +return -EINVAL ; + + vcpu_pmu =kvm_vcpu_has_pmu (vcpu); + dfr0_pmu =id_reg_has_pmu (val,ID_AA64DFR0_PMUVER_SHIFT ,ID_AA64DFR0_PMUVER_8_0 ); +/* Check if there is a conflict with a request via KVM_ARM_VCPU_INIT */ +if (vcpu_pmu ^ dfr0_pmu) +return -EPERM ; + +return 0 ; +} +static void init_id_aa64pfr0_el1_info (struct id_reg_info *id_reg) {u64 limit = id_reg->vcpu_limit_val;
@@ -651,6 +690,23 @@ static void init_id_aa64isar1_el1_info(struct id_reg_info *id_reg) id_reg->vcpu_limit_val &= ~PTRAUTH_MASK ; } +static void init_id_aa64dfr0_el1_info (struct id_reg_info *id_reg) +{ +u64 limit = id_reg->vcpu_limit_val; + +/* Limit guests to PMUv3 for ARMv8.4 */ + limit =cpuid_feature_cap_perfmon_field (limit,ID_AA64DFR0_PMUVER_SHIFT , +ID_AA64DFR0_PMUVER_8_4 ); +/* Limit debug to ARMv8.0 */ + limit &= ~ARM64_FEATURE_MASK (ID_AA64DFR0_DEBUGVER ); + limit |= (FIELD_PREP (ARM64_FEATURE_MASK (ID_AA64DFR0_DEBUGVER ),6 )); + +/* Hide SPE from guests */ + limit &= ~ARM64_FEATURE_MASK (ID_AA64DFR0_PMSVER ); + + id_reg->vcpu_limit_val = limit; +} +static u64 get_reset_id_aa64pfr0_el1 (struct kvm_vcpu *vcpu,const struct id_reg_info *idr) {
@@ -674,6 +730,14 @@ static u64 get_reset_id_aa64isar1_el1(struct kvm_vcpu *vcpu, idr->vcpu_limit_val : (idr->vcpu_limit_val & ~PTRAUTH_MASK); } +static u64 get_reset_id_aa64dfr0_el1 (struct kvm_vcpu *vcpu, +const struct id_reg_info *idr) +{ +return kvm_vcpu_has_pmu (vcpu) ? + idr->vcpu_limit_val : + (idr->vcpu_limit_val & ~(ARM64_FEATURE_MASK (ID_AA64DFR0_PMUVER ))); +} +static struct id_reg_info id_aa64pfr0_el1_info = { .sys_reg =SYS_ID_AA64PFR0_EL1 , .ftr_check_types = S_FCT(ID_AA64PFR0_ASIMD_SHIFT, FCT_LOWER_SAFE) |
@@ -718,6 +782,14 @@ static struct id_reg_info id_aa64mmfr0_el1_info = { .validate = validate_id_aa64mmfr0_el1, }; +static struct id_reg_info id_aa64dfr0_el1_info = { + .sys_reg =SYS_ID_AA64DFR0_EL1 , + .ftr_check_types =S_FCT (ID_AA64DFR0_DOUBLELOCK_SHIFT ,FCT_LOWER_SAFE ), + .init = init_id_aa64dfr0_el1_info, + .validate = validate_id_aa64dfr0_el1, + .get_reset_val = get_reset_id_aa64dfr0_el1, +}; +/* * An ID register that needs special handling to control the value for the * guest must have its own id_reg_info in id_reg_info_table.
@@ -729,6 +801,7 @@ static struct id_reg_info id_aa64mmfr0_el1_info = {static struct id_reg_info *id_reg_info_table[KVM_ARM_ID_REG_MAX_NUM ] = { [IDREG_IDX (SYS_ID_AA64PFR0_EL1 )] = &id_aa64pfr0_el1_info, [IDREG_IDX (SYS_ID_AA64PFR1_EL1 )] = &id_aa64pfr1_el1_info, + [IDREG_IDX (SYS_ID_AA64DFR0_EL1 )] = &id_aa64dfr0_el1_info, [IDREG_IDX (SYS_ID_AA64ISAR0_EL1 )] = &id_aa64isar0_el1_info, [IDREG_IDX (SYS_ID_AA64ISAR1_EL1 )] = &id_aa64isar1_el1_info, [IDREG_IDX (SYS_ID_AA64MMFR0_EL1 )] = &id_aa64mmfr0_el1_info,
@@ -1566,17 +1639,6 @@ static u64 read_id_reg(const struct kvm_vcpu *vcpu,u64 val = raz ?0 :__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id));switch (id) { -case SYS_ID_AA64DFR0_EL1 : -/* Limit debug to ARMv8.0 */ - val &= ~ARM64_FEATURE_MASK (ID_AA64DFR0_DEBUGVER ); - val |=FIELD_PREP (ARM64_FEATURE_MASK (ID_AA64DFR0_DEBUGVER ),6 ); -/* Limit guests to PMUv3 for ARMv8.4 */ - val =cpuid_feature_cap_perfmon_field (val, -ID_AA64DFR0_PMUVER_SHIFT , -kvm_vcpu_has_pmu (vcpu) ?ID_AA64DFR0_PMUVER_8_4 :0 ); -/* Hide SPE from guests */ - val &= ~ARM64_FEATURE_MASK (ID_AA64DFR0_PMSVER ); -break ;case SYS_ID_DFR0_EL1 :/* Limit guests to PMUv3 for ARMv8.4 */ val = cpuid_feature_cap_perfmon_field(val,
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 12/28 KVM: arm64: Make ID_DFR0_EL1 writable
In reply to Reiji WatanabeThis patch adds id_reg_info for ID_DFR0_EL1 to make it writable by userspace.
Return an error if userspace tries to set PerfMon field of the register to a value that conflicts with the PMU configuration.
--- arch/arm64/kvm/sys_regs.c | 58 +++++++++++++++++++++++++++++++-------- 1 file changed, 47 insertions(+), 11 deletions(-)
arch/arm64/kvm/sys_regs.c +47 -11
@@ -654,6 +654,27 @@ static int validate_id_aa64dfr0_el1(struct kvm_vcpu *vcpu,return 0 ; } +static int validate_id_dfr0_el1 (struct kvm_vcpu *vcpu, +const struct id_reg_info *id_reg,u64 val) +{ +bool vcpu_pmu, dfr0_pmu; +unsigned int perfmon; + + perfmon =cpuid_feature_extract_unsigned_field (val,ID_DFR0_PERFMON_SHIFT ); +if (perfmon ==1 || perfmon ==2 ) +/* PMUv1 or PMUv2 is not allowed on ARMv8. */ +return -EINVAL ; + + vcpu_pmu =kvm_vcpu_has_pmu (vcpu); + dfr0_pmu =id_reg_has_pmu (val,ID_DFR0_PERFMON_SHIFT ,ID_DFR0_PERFMON_8_0 ); + +/* Check if there is a conflict with a request via KVM_ARM_VCPU_INIT */ +if (vcpu_pmu ^ dfr0_pmu) +return -EPERM ; + +return 0 ; +} +static void init_id_aa64pfr0_el1_info (struct id_reg_info *id_reg) {u64 limit = id_reg->vcpu_limit_val;
@@ -707,6 +728,15 @@ static void init_id_aa64dfr0_el1_info(struct id_reg_info *id_reg) id_reg->vcpu_limit_val = limit; } +static void init_id_dfr0_el1_info (struct id_reg_info *id_reg) +{ +/* Limit guests to PMUv3 for ARMv8.4 */ + id_reg->vcpu_limit_val = +cpuid_feature_cap_perfmon_field (id_reg->vcpu_limit_val, +ID_DFR0_PERFMON_SHIFT , +ID_DFR0_PERFMON_8_4 ); +} +static u64 get_reset_id_aa64pfr0_el1 (struct kvm_vcpu *vcpu,const struct id_reg_info *idr) {
@@ -738,6 +768,14 @@ static u64 get_reset_id_aa64dfr0_el1(struct kvm_vcpu *vcpu, (idr->vcpu_limit_val & ~(ARM64_FEATURE_MASK (ID_AA64DFR0_PMUVER ))); } +static u64 get_reset_id_dfr0_el1 (struct kvm_vcpu *vcpu, +const struct id_reg_info *idr) +{ +return kvm_vcpu_has_pmu (vcpu) ? + idr->vcpu_limit_val : + (idr->vcpu_limit_val & ~(ARM64_FEATURE_MASK (ID_DFR0_PERFMON ))); +} +static struct id_reg_info id_aa64pfr0_el1_info = { .sys_reg =SYS_ID_AA64PFR0_EL1 , .ftr_check_types = S_FCT(ID_AA64PFR0_ASIMD_SHIFT, FCT_LOWER_SAFE) |
@@ -790,6 +828,13 @@ static struct id_reg_info id_aa64dfr0_el1_info = { .get_reset_val = get_reset_id_aa64dfr0_el1, }; +static struct id_reg_info id_dfr0_el1_info = { + .sys_reg =SYS_ID_DFR0_EL1 , + .init = init_id_dfr0_el1_info, + .validate = validate_id_dfr0_el1, + .get_reset_val = get_reset_id_dfr0_el1, +}; +/* * An ID register that needs special handling to control the value for the * guest must have its own id_reg_info in id_reg_info_table.
@@ -799,6 +844,7 @@ static struct id_reg_info id_aa64dfr0_el1_info = {*/ #define GET_ID_REG_INFO (id) (id_reg_info_table[IDREG_IDX(id)])static struct id_reg_info *id_reg_info_table[KVM_ARM_ID_REG_MAX_NUM ] = { + [IDREG_IDX (SYS_ID_DFR0_EL1 )] = &id_dfr0_el1_info, [IDREG_IDX (SYS_ID_AA64PFR0_EL1 )] = &id_aa64pfr0_el1_info, [IDREG_IDX (SYS_ID_AA64PFR1_EL1 )] = &id_aa64pfr1_el1_info, [IDREG_IDX (SYS_ID_AA64DFR0_EL1 )] = &id_aa64dfr0_el1_info,
@@ -1636,18 +1682,8 @@ static u64 read_id_reg(const struct kvm_vcpu *vcpu, struct sys_reg_desc const *r, bool raz) {u32 id =reg_to_encoding (r); -u64 val = raz ?0 :__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id)); - -switch (id) { -case SYS_ID_DFR0_EL1 : -/* Limit guests to PMUv3 for ARMv8.4 */ - val =cpuid_feature_cap_perfmon_field (val, -ID_DFR0_PERFMON_SHIFT , -kvm_vcpu_has_pmu (vcpu) ?ID_DFR0_PERFMON_8_4 :0 ); -break ; - } -return val; +return raz ?0 :__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id)); } static unsigned int id_visibility(const struct kvm_vcpu *vcpu,
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 13/28 KVM: arm64: Make ID_DFR1_EL1 writable
In reply to Reiji WatanabeThis patch adds id_reg_info for ID_DFR1_EL1 to make it writable by userspace.
--- arch/arm64/kvm/sys_regs.c | 6 ++++++ 1 file changed, 6 insertions(+)
arch/arm64/kvm/sys_regs.c +6 -0
@@ -835,6 +835,11 @@ static struct id_reg_info id_dfr0_el1_info = { .get_reset_val = get_reset_id_dfr0_el1, }; +static struct id_reg_info id_dfr1_el1_info = { + .sys_reg =SYS_ID_DFR1_EL1 , + .ftr_check_types =S_FCT (ID_DFR1_MTPMU_SHIFT ,FCT_LOWER_SAFE ), +}; +/* * An ID register that needs special handling to control the value for the * guest must have its own id_reg_info in id_reg_info_table.
@@ -845,6 +850,7 @@ static struct id_reg_info id_dfr0_el1_info = {#define GET_ID_REG_INFO (id) (id_reg_info_table[IDREG_IDX(id)])static struct id_reg_info *id_reg_info_table[KVM_ARM_ID_REG_MAX_NUM ] = { [IDREG_IDX (SYS_ID_DFR0_EL1 )] = &id_dfr0_el1_info, + [IDREG_IDX (SYS_ID_DFR1_EL1 )] = &id_dfr1_el1_info, [IDREG_IDX (SYS_ID_AA64PFR0_EL1 )] = &id_aa64pfr0_el1_info, [IDREG_IDX (SYS_ID_AA64PFR1_EL1 )] = &id_aa64pfr1_el1_info, [IDREG_IDX (SYS_ID_AA64DFR0_EL1 )] = &id_aa64dfr0_el1_info,
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 14/28 KVM: arm64: Make ID_MMFR0_EL1 writable
In reply to Reiji WatanabeThis patch adds id_reg_info for ID_MMFR0_EL1 to make it writable by userspace.
--- arch/arm64/kvm/sys_regs.c | 7 +++++++ 1 file changed, 7 insertions(+)
arch/arm64/kvm/sys_regs.c +7 -0
@@ -840,6 +840,12 @@ static struct id_reg_info id_dfr1_el1_info = { .ftr_check_types = S_FCT(ID_DFR1_MTPMU_SHIFT, FCT_LOWER_SAFE), }; +static struct id_reg_info id_mmfr0_el1_info = { + .sys_reg =SYS_ID_MMFR0_EL1 , + .ftr_check_types =S_FCT (ID_MMFR0_INNERSHR_SHIFT ,FCT_LOWER_SAFE ) | +S_FCT (ID_MMFR0_OUTERSHR_SHIFT ,FCT_LOWER_SAFE ), +}; +/* * An ID register that needs special handling to control the value for the * guest must have its own id_reg_info in id_reg_info_table.
@@ -850,6 +856,7 @@ static struct id_reg_info id_dfr1_el1_info = {#define GET_ID_REG_INFO (id) (id_reg_info_table[IDREG_IDX(id)])static struct id_reg_info *id_reg_info_table[KVM_ARM_ID_REG_MAX_NUM ] = { [IDREG_IDX (SYS_ID_DFR0_EL1 )] = &id_dfr0_el1_info, + [IDREG_IDX (SYS_ID_MMFR0_EL1 )] = &id_mmfr0_el1_info, [IDREG_IDX (SYS_ID_DFR1_EL1 )] = &id_dfr1_el1_info, [IDREG_IDX (SYS_ID_AA64PFR0_EL1 )] = &id_aa64pfr0_el1_info, [IDREG_IDX (SYS_ID_AA64PFR1_EL1 )] = &id_aa64pfr1_el1_info,
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 15/28 KVM: arm64: Make MVFR1_EL1 writable
In reply to Reiji WatanabeThis patch adds id_reg_info for MVFR1_EL1 to make it writable by userspace.
There are only a few valid combinations of values that can be set for FPHP and SIMDHP fields according to Arm ARM. Return an error when userspace tries to set those fields to values that don't match any of the valid combinations.
--- arch/arm64/kvm/sys_regs.c | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+)
arch/arm64/kvm/sys_regs.c +36 -0
@@ -675,6 +675,36 @@ static int validate_id_dfr0_el1(struct kvm_vcpu *vcpu,return 0 ; } +static int validate_mvfr1_el1 (struct kvm_vcpu *vcpu, +const struct id_reg_info *id_reg,u64 val) +{ +unsigned int fphp, simdhp; +struct fphp_simdhp { +unsigned int fphp; +unsigned int simdhp; + }; +/* Permitted fphp/simdhp value combinations according to Arm ARM */ +struct fphp_simdhp valid_fphp_simdhp[3 ] = {{0 ,0 }, {2 ,1 }, {3 ,2 }}; +int i; +bool is_valid_fphp_simdhp = false; + + fphp =cpuid_feature_extract_unsigned_field (val,MVFR1_FPHP_SHIFT ); + simdhp =cpuid_feature_extract_unsigned_field (val,MVFR1_SIMDHP_SHIFT ); + +for (i =0 ; i <ARRAY_SIZE (valid_fphp_simdhp); i++) { +if (valid_fphp_simdhp[i].fphp == fphp && + valid_fphp_simdhp[i].simdhp == simdhp) { + is_valid_fphp_simdhp = true; +break ; + } + } + +if (!is_valid_fphp_simdhp) +return -EINVAL ; + +return 0 ; +} +static void init_id_aa64pfr0_el1_info (struct id_reg_info *id_reg) {u64 limit = id_reg->vcpu_limit_val;
@@ -846,6 +876,11 @@ static struct id_reg_info id_mmfr0_el1_info = { S_FCT(ID_MMFR0_OUTERSHR_SHIFT, FCT_LOWER_SAFE), }; +static struct id_reg_info mvfr1_el1_info = { + .sys_reg =SYS_MVFR1_EL1 , + .validate = validate_mvfr1_el1, +}; +/* * An ID register that needs special handling to control the value for the * guest must have its own id_reg_info in id_reg_info_table.
@@ -857,6 +892,7 @@ static struct id_reg_info id_mmfr0_el1_info = {static struct id_reg_info *id_reg_info_table[KVM_ARM_ID_REG_MAX_NUM ] = { [IDREG_IDX (SYS_ID_DFR0_EL1 )] = &id_dfr0_el1_info, [IDREG_IDX (SYS_ID_MMFR0_EL1 )] = &id_mmfr0_el1_info, + [IDREG_IDX (SYS_MVFR1_EL1 )] = &mvfr1_el1_info, [IDREG_IDX (SYS_ID_DFR1_EL1 )] = &id_dfr1_el1_info, [IDREG_IDX (SYS_ID_AA64PFR0_EL1 )] = &id_aa64pfr0_el1_info, [IDREG_IDX (SYS_ID_AA64PFR1_EL1 )] = &id_aa64pfr1_el1_info,
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 16/28 KVM: arm64: Make ID registers without id_reg_info writable
In reply to Reiji WatanabeMake ID registers that don't have id_reg_info writable.
--- arch/arm64/kvm/sys_regs.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)
arch/arm64/kvm/sys_regs.c +2 -6
@@ -1836,16 +1836,12 @@ static int __set_id_reg(struct kvm_vcpu *vcpu,if (err)return err; -/* Don't allow to change the reg unless the reg has id_reg_info */ -if (val !=read_id_reg (vcpu, rd, raz) && !GET_ID_REG_INFO (encoding)) -return -EINVAL ; -/* Don't allow to change the reg after the first KVM_RUN. */ -if (vcpu->arch.has_run_once) +if ((val !=read_id_reg (vcpu, rd, raz)) && vcpu->arch.has_run_once)return -EINVAL ;if (raz) -return 0 ; +return (val ==0 ) ?0 : -EINVAL ; err =validate_id_reg (vcpu, rd, val);if (err)
Signature · 1 line
2.33.1.1089.g2158813163f-goog
RFC PATCH v2 17/28 KVM: arm64: Add consistency checking for frac fields of ID registers
In reply to Reiji WatanabeFeature fractional field of an ID register cannot be simply validated at KVM_SET_ONE_REG because its validity depends on its (main) feature field value, which could be in a different ID register (and might be set later).
Validate fractional fields at the first KVM_RUN instead.
--- arch/arm64/kvm/sys_regs.c | 121 ++++++++++++++++++++++++++++++++++++-- 1 file changed, 117 insertions(+), 4 deletions(-)
arch/arm64/kvm/sys_regs.c +117 -4
@@ -817,9 +817,6 @@ static struct id_reg_info id_aa64pfr0_el1_info = {static struct id_reg_info id_aa64pfr1_el1_info = { .sys_reg =SYS_ID_AA64PFR1_EL1 , - .ftr_check_types =U_FCT (ID_AA64PFR1_RASFRAC_SHIFT ,FCT_IGNORE ) | -U_FCT (ID_AA64PFR1_MPAMFRAC_SHIFT ,FCT_IGNORE ) | -U_FCT (ID_AA64PFR1_CSV2FRAC_SHIFT ,FCT_IGNORE ), .init = init_id_aa64pfr1_el1_info, .validate = validate_id_aa64pfr1_el1, .get_reset_val = get_reset_id_aa64pfr1_el1,
@@ -3407,10 +3404,86 @@ int kvm_arm_copy_sys_reg_indices(struct kvm_vcpu *vcpu, u64 __user *uindices)return write_demux_regids (uindices); } +/* ID register's fractional field information with its feature field. */ +struct feature_frac { +u32 id; +u32 shift; +u32 frac_id; +u32 frac_shift; +u8 frac_ftr_check; +}; + +static struct feature_frac feature_frac_table[] = { + { + .frac_id =SYS_ID_AA64PFR1_EL1 , + .frac_shift =ID_AA64PFR1_RASFRAC_SHIFT , + .id =SYS_ID_AA64PFR0_EL1 , + .shift =ID_AA64PFR0_RAS_SHIFT , + }, + { + .frac_id =SYS_ID_AA64PFR1_EL1 , + .frac_shift =ID_AA64PFR1_MPAMFRAC_SHIFT , + .id =SYS_ID_AA64PFR0_EL1 , + .shift =ID_AA64PFR0_MPAM_SHIFT , + }, + { + .frac_id =SYS_ID_AA64PFR1_EL1 , + .frac_shift =ID_AA64PFR1_CSV2FRAC_SHIFT , + .id =SYS_ID_AA64PFR0_EL1 , + .shift =ID_AA64PFR0_CSV2_SHIFT , + }, +}; + +/* +* Return non-zero if the feature/fractional fields pair are not +* supported. Return zero otherwise. +* This function only checks fractional feature field and assumes +* the feature field is valid. +*/ +static int vcpu_id_reg_feature_frac_check (const struct kvm_vcpu *vcpu, +const struct feature_frac *ftr_frac) +{ +u32 id; +int fval, flim, ret; +u64 val, lim, mask; +const struct id_reg_info *id_reg; +bool sign =FCT_SIGN (ftr_frac->frac_ftr_check); +enum feature_check_type type =FCT_TYPE (ftr_frac->frac_ftr_check); + +/* Check if the feature field value is same as the limit */ + id = ftr_frac->id; + id_reg =GET_ID_REG_INFO (id); + + val =__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id)); + lim = id_reg ? id_reg->vcpu_limit_val :read_sanitised_ftr_reg (id); + + mask = (u64 )ARM64_FEATURE_FIELD_MASK << ftr_frac->shift; +if ((val & mask) != (lim & mask)) +/* +* The feature level is smaller than the limit. +* Any fractional version should be fine. +*/ +return 0 ; + +/* Check the fractional feature field */ + id = ftr_frac->frac_id; + id_reg =GET_ID_REG_INFO (id); + + val =__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id)); + fval =cpuid_feature_extract_field (val, ftr_frac->frac_shift, sign); + + lim = id_reg ? id_reg->vcpu_limit_val :read_sanitised_ftr_reg (id); + flim =cpuid_feature_extract_field (lim, ftr_frac->frac_shift, sign); + + ret =arm64_check_feature_one (type, fval, flim); +return ret ? -E2BIG :0 ; +} +int kvm_id_regs_consistency_check (const struct kvm_vcpu *vcpu) { -int i; +int i, err;const struct kvm_vcpu *t_vcpu; +const struct feature_frac *frac;/* * Make sure vcpu->arch.has_run_once is visible for others so that
@@ -3431,6 +3504,17 @@ int kvm_id_regs_consistency_check(const struct kvm_vcpu *vcpu) KVM_ARM_ID_REG_MAX_NUM))return -EINVAL ; } + +/* +* Check ID registers' fractional fields, which aren't checked +* at KVM_SET_ONE_REG. +*/ +for (i =0 ; i <ARRAY_SIZE (feature_frac_table); i++) { + frac = &feature_frac_table[i]; + err =vcpu_id_reg_feature_frac_check (vcpu, frac); +if (err) +return err; + }return 0 ; }
@@ -3438,6 +3522,9 @@ static void id_reg_info_init_all(void) {int i;struct id_reg_info *id_reg; +struct feature_frac *frac; +u64 mask =ARM64_FEATURE_FIELD_MASK ; +u64 org;for (i =0 ; i <ARRAY_SIZE (id_reg_info_table); i++) { id_reg = (struct id_reg_info *)id_reg_info_table[i];
@@ -3446,6 +3533,32 @@ static void id_reg_info_init_all(void)id_reg_info_init (id_reg); } + +for (i =0 ; i <ARRAY_SIZE (feature_frac_table); i++) { + frac = &feature_frac_table[i]; + id_reg =GET_ID_REG_INFO (frac->frac_id); + +/* +* An ID register that has fractional fields is expected +* to have its own id_reg_info. +*/ +if (WARN_ON_ONCE (!id_reg)) +continue ; + +/* +* Update the id_reg's ftr_check_types for the fractional +* field with FCT_IGNORE so that the field won't be validated +* when the ID register is set by userspace, which could +* temporarily cause an inconsistency if its (main) feature +* field is not set yet. Save the original ftr_check_types +* for the fractional field to validate the field later. +*/ + org = (id_reg->ftr_check_types >> frac->frac_shift) & mask; + id_reg->ftr_check_types &= ~(mask << frac->frac_shift); + id_reg->ftr_check_types |= +MAKE_FCT (frac->frac_shift,FCT_IGNORE ,FCT_SIGN (org)); + frac->frac_ftr_check = org; + } }void kvm_sys_reg_table_init (void )
Signature · 6 lines
2.33.1.1089.g2158813163f-goog _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
RFC PATCH v2 18/28 KVM: arm64: Introduce KVM_CAP_ARM_ID_REG_WRITABLE capability
In reply to Reiji WatanabeIntroduce a new capability KVM_CAP_ARM_ID_REG_WRITABLE to indicate that ID registers are writable by userspace.
--- Documentation/virt/kvm/api.rst | 8 ++++++++ arch/arm64/kvm/arm.c | 1 + include/uapi/linux/kvm.h | 1 + 3 files changed, 10 insertions(+)
Documentation/virt/kvm/api.rst +8 -0
@@ -7265,3 +7265,11 @@ The argument to KVM_ENABLE_CAP is also a bitmask, and must be a subset of the result of KVM_CHECK_EXTENSION. KVM will forward to userspace the hypercalls whose corresponding bit is in the argument, and return ENOSYS for the others. + +8.35 KVM_CAP_ARM_ID_REG_WRITABLE +-------------------------------- + +:Architectures: arm64 + +This capability indicates that userspace can modify the ID registers +via KVM_SET_ONE_REG ioctl.
arch/arm64/kvm/arm.c +1 -0
@@ -197,6 +197,7 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)case KVM_CAP_SET_GUEST_DEBUG :case KVM_CAP_VCPU_ATTRIBUTES :case KVM_CAP_PTP_KVM : +case KVM_CAP_ARM_ID_REG_WRITABLE : r =1 ;break ;case KVM_CAP_SET_GUEST_DEBUG2 :
include/uapi/linux/kvm.h +1 -0
@@ -1112,6 +1112,7 @@ struct kvm_ppc_resize_hpt {#define KVM_CAP_BINARY_STATS_FD 203#define KVM_CAP_EXIT_ON_EMULATION_FAILURE 204#define KVM_CAP_ARM_MTE 205 +#define KVM_CAP_ARM_ID_REG_WRITABLE 206#ifdef KVM_CAP_IRQ_ROUTING
Signature · 6 lines
2.33.1.1089.g2158813163f-goog _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
Re: [RFC PATCH v2 18/28] KVM: arm64: Introduce KVM_CAP_ARM_ID_REG_WRITABLE capability
Quoted 15 lines · Reiji Watanabe
Introduce a new capability
KVM_CAP_ARM_ID_REG_WRITABLEto indicate that ID registers are writable by userspace.Signed-off-by Reiji Watanabe <[email protected]>--- Documentation/virt/kvm/api.rst | 8 ++++++++ arch/arm64/kvm/arm.c | 1 + include/uapi/linux/kvm.h | 1 + 3 files changed, 10 insertions(+)Documentation/virt/kvm/api.rst +0
-0
Documentation/virt/kvm/api.rst The argument to KVM_ENABLE_CAP is also a bitmask, and must be a subset · line 7270
Quoted 6 lines
Documentation/virt/kvm/api.rst +3
-0@@ -7265,3 +7265,11 @@ The argument to KVM_ENABLE_CAP is also a bitmask, and must be a subset of the result of KVM_CHECK_EXTENSION. KVM will forward to userspace the hypercalls whose corresponding bit is in the argument, and return ENOSYS for the others. + +8.35 KVM_CAP_ARM_ID_REG_WRITABLE +--------------------------------
ID registers are technically already writable, KVM just rejects any value other than what it derives from sanitising the host ID registers. I agree that the nuance being added warrants a KVM_CAP, as it informs userspace it can deliberately configure ID registers with a more limited value than what KVM returns.
KVM_CAP_ARM_ID_REG_CONFIGURABLE maybe? Naming is hard :)
--
Thanks,
Oliver
Re: [RFC PATCH v2 18/28] KVM: arm64: Introduce KVM_CAP_ARM_ID_REG_WRITABLE capability
Quoted 30 lines · Oliver Upton
Quoted 15 lines · Reiji Watanabe
Introduce a new capability
KVM_CAP_ARM_ID_REG_WRITABLEto indicate that ID registers are writable by userspace.Signed-off-by Reiji Watanabe <[email protected]>--- Documentation/virt/kvm/api.rst | 8 ++++++++ arch/arm64/kvm/arm.c | 1 + include/uapi/linux/kvm.h | 1 + 3 files changed, 10 insertions(+)Documentation/virt/kvm/api.rst +0
-0Documentation/virt/kvm/api.rst The argument to KVM_ENABLE_CAP is also a bitmask, and must be a subset · line 7270
Quoted 6 lines
Documentation/virt/kvm/api.rst +3
-0@@ -7265,3 +7265,11 @@ The argument to KVM_ENABLE_CAP is also a bitmask, and must be a subset of the result of KVM_CHECK_EXTENSION. KVM will forward to userspace the hypercalls whose corresponding bit is in the argument, and return ENOSYS for the others. + +8.35 KVM_CAP_ARM_ID_REG_WRITABLE +--------------------------------ID registers are technically already writable, KVM just rejects any value other than what it derives from sanitising the host ID registers. I agree that the nuance being added warrants a
KVM_CAP, as it informs userspace it can deliberately configure ID registers with a more limited value than what KVM returns.
Quoted 1 line
KVM_CAP_ARM_ID_REG_CONFIGURABLEmaybe? Naming is hard :)
Thank you for the suggestion. Yes, that sounds better. I will change the name as you suggested.
Regards,
Reiji
RFC PATCH v2 19/28 KVM: arm64: Use vcpu->arch cptr_el2 to track value of cptr_el2 for VHE
In reply to Reiji WatanabeTrack the baseline guest value for cptr_el2 in struct kvm_vcpu_arch for VHE. Use this value when setting cptr_el2 for the guest.
Currently this value is unchanged, but the following patches will set trapping bits based on features supported for the guest.
No functional change intended.
--- arch/arm64/include/asm/kvm_arm.h | 16 ++++++++++++++++ arch/arm64/kvm/arm.c | 5 ++++- arch/arm64/kvm/hyp/vhe/switch.c | 14 ++------------ 3 files changed, 22 insertions(+), 13 deletions(-)
arch/arm64/include/asm/kvm_arm.h +16 -0
@@ -288,6 +288,22 @@ GENMASK(19, 14) | \ BIT(11)) +/* +* With VHE (HCR.E2H == 1), accesses to CPACR_EL1 are routed to +* CPTR_EL2. In general, CPACR_EL1 has the same layout as CPTR_EL2, +* except for some missing controls, such as TAM. +* In this case, CPTR_EL2.TAM has the same position with or without +* VHE (HCR.E2H == 1) which allows us to use here the CPTR_EL2.TAM +* shift value for trapping the AMU accesses. +*/ +#define CPTR_EL2_VHE_GUEST_DEFAULT (CPACR_EL1_TTA | CPTR_EL2_TAM) + +/* +* Bits that are copied from vcpu->arch.cptr_el2 to set cptr_el2 for +* guest with VHE. +*/ +#define CPTR_EL2_VHE_GUEST_TRACKED_MASK (CPACR_EL1_TTA | CPTR_EL2_TAM) +/* Hyp Debug Configuration Register bits */ #define MDCR_EL2_E2TB_MASK (UL(0x3))#define MDCR_EL2_E2TB_SHIFT (UL(24))
arch/arm64/kvm/arm.c +4 -1
@@ -1109,7 +1109,10 @@ static int kvm_arch_vcpu_ioctl_vcpu_init(struct kvm_vcpu *vcpu, }vcpu_reset_hcr (vcpu); - vcpu->arch.cptr_el2 =CPTR_EL2_DEFAULT ; +if (has_vhe ()) + vcpu->arch.cptr_el2 =CPTR_EL2_VHE_GUEST_DEFAULT ; +else + vcpu->arch.cptr_el2 =CPTR_EL2_DEFAULT ;/* * Handle the "start in power-off" case.
arch/arm64/kvm/hyp/vhe/switch.c +2 -12
@@ -38,20 +38,10 @@ static void __activate_traps(struct kvm_vcpu *vcpu)___activate_traps (vcpu); val =read_sysreg (cpacr_el1); - val |=CPACR_EL1_TTA ; + val &= ~CPTR_EL2_VHE_GUEST_TRACKED_MASK ; + val |= (vcpu->arch.cptr_el2 &CPTR_EL2_VHE_GUEST_TRACKED_MASK ); val &= ~CPACR_EL1_ZEN ; -/* -* With VHE (HCR.E2H == 1), accesses to CPACR_EL1 are routed to -* CPTR_EL2. In general, CPACR_EL1 has the same layout as CPTR_EL2, -* except for some missing controls, such as TAM. -* In this case, CPTR_EL2.TAM has the same position with or without -* VHE (HCR.E2H == 1) which allows us to use here the CPTR_EL2.TAM -* shift value for trapping the AMU accesses. -*/ - - val |=CPTR_EL2_TAM ; -if (update_fp_enabled (vcpu)) {if (vcpu_has_sve (vcpu)) val |=CPACR_EL1_ZEN ;
Signature · 6 lines
2.33.1.1089.g2158813163f-goog _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
RFC PATCH v2 20/28 KVM: arm64: Use vcpu->arch.mdcr_el2 to track value of mdcr_el2
In reply to Reiji WatanabeTrack the baseline guest value for mdcr_el2 in struct kvm_vcpu_arch. Use this value when setting mdcr_el2 for the guest.
Currently this value is unchanged, but the following patches will set trapping bits based on features supported for the guest.
No functional change intended.
--- arch/arm64/include/asm/kvm_arm.h | 16 ++++++++++++++++ arch/arm64/kvm/arm.c | 1 + arch/arm64/kvm/debug.c | 13 ++++--------- 3 files changed, 21 insertions(+), 9 deletions(-)
arch/arm64/include/asm/kvm_arm.h +16 -0
@@ -332,6 +332,22 @@ BIT(18) | \ GENMASK(16, 15)) +/* +* The default value for the guest below also clears MDCR_EL2_E2PB_MASK +* and MDCR_EL2_E2TB_MASK to disable guest access to the profiling and +* trace buffers. +*/ +#define MDCR_GUEST_FLAGS_DEFAULT \ + (MDCR_EL2_TPM | MDCR_EL2_TPMS | MDCR_EL2_TTRF | \ + MDCR_EL2_TPMCR | MDCR_EL2_TDRA | MDCR_EL2_TDOSA) + +/* Bits that are copied from vcpu->arch.mdcr_el2 to set mdcr_el2 for guest. */ +#define MDCR_GUEST_FLAGS_TRACKED_MASK \ + (MDCR_EL2_TPM | MDCR_EL2_TPMS | MDCR_EL2_TTRF | \ + MDCR_EL2_TPMCR | MDCR_EL2_TDRA | MDCR_EL2_TDOSA | \ + (MDCR_EL2_E2PB_MASK << MDCR_EL2_E2PB_SHIFT)) + +/* For compatibility with fault code shared with 32-bit */ #define FSC_FAULT ESR_ELx_FSC_FAULT#define FSC_ACCESS ESR_ELx_FSC_ACCESS
arch/arm64/kvm/arm.c +1 -0
@@ -1109,6 +1109,7 @@ static int kvm_arch_vcpu_ioctl_vcpu_init(struct kvm_vcpu *vcpu, }vcpu_reset_hcr (vcpu); + vcpu->arch.mdcr_el2 =MDCR_GUEST_FLAGS_DEFAULT ;if (has_vhe ()) vcpu->arch.cptr_el2 =CPTR_EL2_VHE_GUEST_DEFAULT ;else
arch/arm64/kvm/debug.c +4 -9
@@ -84,16 +84,11 @@ void kvm_arm_init_debug(void)static void kvm_arm_setup_mdcr_el2 (struct kvm_vcpu *vcpu) {/* -* This also clears MDCR_EL2_E2PB_MASK and MDCR_EL2_E2TB_MASK -* to disable guest access to the profiling and trace buffers +* Keep the vcpu->arch.mdcr_el2 bits that are specified by +* MDCR_GUEST_FLAGS_TRACKED_MASK. */ - vcpu->arch.mdcr_el2 =__this_cpu_read (mdcr_el2) &MDCR_EL2_HPMN_MASK ; - vcpu->arch.mdcr_el2 |= (MDCR_EL2_TPM | -MDCR_EL2_TPMS | -MDCR_EL2_TTRF | -MDCR_EL2_TPMCR | -MDCR_EL2_TDRA | -MDCR_EL2_TDOSA ); + vcpu->arch.mdcr_el2 &=MDCR_GUEST_FLAGS_TRACKED_MASK ; + vcpu->arch.mdcr_el2 |=__this_cpu_read (mdcr_el2) &MDCR_EL2_HPMN_MASK ;/* Is the VM being debugged by userspace? */ if (vcpu->guest_debug)
Signature · 6 lines
2.33.1.1089.g2158813163f-goog _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
RFC PATCH v2 21/28 KVM: arm64: Introduce framework to trap disabled features
In reply to Reiji WatanabeWhen a CPU feature that is supported on the host is not exposed to its guest, emulating a real CPU's behavior (by trapping or disabling guest's using the feature) is generally a desirable behavior (when it's possible without any or little side effect).
Introduce feature_config_ctrl structure, which manages feature information to program configuration register to trap or disable the feature when the feature is not exposed to the guest, and functions that uses the structure to activate trapping the feature.
At present, no feature has feature_config_ctrl yet and the following patches will add the feature_config_ctrl for several features.
--- arch/arm64/kvm/sys_regs.c | 121 +++++++++++++++++++++++++++++++++++++- 1 file changed, 120 insertions(+), 1 deletion(-)
arch/arm64/kvm/sys_regs.c +120 -1
@@ -374,8 +374,38 @@ static int arm64_check_features(u64 check_types, u64 val, u64 lim) (cpuid_feature_extract_unsigned_field (val,ID_AA64ISAR1_GPI_SHIFT ) >= \ ID_AA64ISAR1_GPI_IMP_DEF) +enum vcpu_config_reg { +VCPU_HCR_EL2 =1 , +VCPU_MDCR_EL2 , +VCPU_CPTR_EL2 , +}; + +/* +* Feature information to program configuration register to trap or disable +* guest's using a feature when the feature is not exposed to the guest. +*/ +struct feature_config_ctrl { +/* ID register/field for the feature */ +u32 ftr_reg;/* ID register */ +bool ftr_signed;/* Is the feature field signed ? */ +u8 ftr_shift;/* Field of ID register for the feature */ +s8 ftr_min;/* Min value that indicate the feature */ + +/* +* Function to check trapping is needed. This is used when the above +* fields are not enough to determine if trapping is needed. +*/ +bool (*ftr_need_trap)(struct kvm_vcpu *vcpu); + +/* Configuration register information to trap the feature. */ +enum vcpu_config_reg cfg_reg;/* Configuration register */ +u64 cfg_mask;/* Field of the configuration register */ +u64 cfg_val;/* Value that are set for the field */ +}; +struct id_reg_info {u32 sys_reg;/* Register ID */ +u64 sys_val;/* Sanitized system value */ /* * Limit value of the register for a vcpu. The value is the sanitized
@@ -408,11 +438,15 @@ struct id_reg_info {/* Return the reset value of the register for the vCPU */ u64 (*get_reset_val)(struct kvm_vcpu *vcpu,const struct id_reg_info *id_reg); + +/* Information to trap features that are disabled for the guest */ +const struct feature_config_ctrl *(*trap_features)[]; };static void id_reg_info_init (struct id_reg_info *id_reg) { - id_reg->vcpu_limit_val =read_sanitised_ftr_reg (id_reg->sys_reg); + id_reg->sys_val =read_sanitised_ftr_reg (id_reg->sys_reg); + id_reg->vcpu_limit_val = id_reg->sys_val;if (id_reg->init) id_reg->init (id_reg); }
@@ -928,6 +962,47 @@ static int validate_id_reg(struct kvm_vcpu *vcpu,return err; } +static void feature_trap_activate (struct kvm_vcpu *vcpu, +const struct feature_config_ctrl *config) +{ +u64 *reg_ptr, reg_val; + +switch (config->cfg_reg) { +case VCPU_HCR_EL2 : + reg_ptr = &vcpu->arch.hcr_el2; +break ; +case VCPU_MDCR_EL2 : + reg_ptr = &vcpu->arch.mdcr_el2; +break ; +case VCPU_CPTR_EL2 : + reg_ptr = &vcpu->arch.cptr_el2; +break ; + } + +/* Update cfg_mask fields with cfg_val */ + reg_val = (*reg_ptr & ~config->cfg_mask); + reg_val |= config->cfg_val; + *reg_ptr = reg_val; +} + +static inline bool feature_avail (const struct feature_config_ctrl *ctrl, +u64 id_val) +{ +int field_val =cpuid_feature_extract_field (id_val, + ctrl->ftr_shift, ctrl->ftr_signed); + +return (field_val >= ctrl->ftr_min); +} + +static inline bool vcpu_feature_is_available (struct kvm_vcpu *vcpu, +const struct feature_config_ctrl *ctrl) +{ +u64 val; + + val =__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (ctrl->ftr_reg)); +return feature_avail (ctrl, val); +} +/* * ARMv8.1 mandates at least a trivial LORegion implementation, where all the * RW registers are RES0 (which we can implement as RAZ/WI). On an ARMv8.0
@@ -1781,6 +1856,42 @@ static int reg_from_user(u64 *val, const void __user *uaddr, u64 id);static int reg_to_user (void __user *uaddr,const u64 *val,u64 id);static u64 sys_reg_to_index (const struct sys_reg_desc *reg); +static void id_reg_features_trap_activate (struct kvm_vcpu *vcpu, +const struct id_reg_info *id_reg) +{ +u64 val; +int i =0 ; +const struct feature_config_ctrl **ctrlp_array, *ctrl; + +if (!id_reg || !id_reg->trap_features) +/* No information to trap a feature */ +return ; + + val =__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (id_reg->sys_reg)); +if (val == id_reg->sys_val) +/* No feature needs to be trapped (no feature is disabled). */ +return ; + + ctrlp_array = *id_reg->trap_features; +while ((ctrl = ctrlp_array[i++]) !=NULL ) { +if (ctrl->ftr_need_trap && ctrl->ftr_need_trap (vcpu)) { +feature_trap_activate (vcpu, ctrl); +continue ; + } + +if (!feature_avail (ctrl, id_reg->sys_val)) +/* The feature is not supported on the host. */ +continue ; + +if (feature_avail (ctrl, val)) +/* The feature is enabled for the guest. */ +continue ; + +/* The feature is supported but disabled. */ +feature_trap_activate (vcpu, ctrl); + } +} +/* Visibility overrides for SVE-specific control registers */ static unsigned int sve_visibility (const struct kvm_vcpu *vcpu,const struct sys_reg_desc *rd)
@@ -3404,6 +3515,14 @@ int kvm_arm_copy_sys_reg_indices(struct kvm_vcpu *vcpu, u64 __user *uindices)return write_demux_regids (uindices); } +void kvm_vcpu_id_regs_trap_activate (struct kvm_vcpu *vcpu) +{ +int i; + +for (i =0 ; i <ARRAY_SIZE (id_reg_info_table); i++) +id_reg_features_trap_activate (vcpu, id_reg_info_table[i]); +} +/* ID register's fractional field information with its feature field. */ struct feature_frac {u32 id;
Signature · 6 lines
2.33.1.1089.g2158813163f-goog _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
RFC PATCH v2 22/28 KVM: arm64: Trap disabled features of ID_AA64PFR0_EL1
In reply to Reiji WatanabeAdd feature_config_ctrl for RAS and AMU, which are indicated in ID_AA64PFR0_EL1, to program configuration registers to trap guest's using those features when they are not exposed to the guest.
Introduce trap_ras_regs() to change a behavior of guest's access to the registers, which is currently raz/wi, depending on the feature's availability for the guest (and inject undefined instruction exception when guest's RAS register access are trapped and RAS is not exposed to the guest). In order to keep the current visibility of the RAS registers from userspace (always visible), a visibility function for RAS registers is not added.
No code is added for AMU's access/visibility handler because the current code already injects the exception for Guest's AMU register access unconditionally because AMU is never exposed to the guest.
--- arch/arm64/kvm/sys_regs.c | 54 +++++++++++++++++++++++++++++++++------ 1 file changed, 46 insertions(+), 8 deletions(-)
arch/arm64/kvm/sys_regs.c +46 -8
@@ -403,6 +403,27 @@ struct feature_config_ctrl {u64 cfg_val;/* Value that are set for the field */ }; +/* For ID_AA64PFR0_EL1 */ +static struct feature_config_ctrl ftr_ctrl_ras = { + .ftr_reg =SYS_ID_AA64PFR0_EL1 , + .ftr_shift =ID_AA64PFR0_RAS_SHIFT , + .ftr_min =ID_AA64PFR0_RAS_V1 , + .ftr_signed =FTR_UNSIGNED , + .cfg_reg =VCPU_HCR_EL2 , + .cfg_mask = (HCR_TERR |HCR_TEA |HCR_FIEN ), + .cfg_val = (HCR_TERR |HCR_TEA ), +}; + +static struct feature_config_ctrl ftr_ctrl_amu = { + .ftr_reg =SYS_ID_AA64PFR0_EL1 , + .ftr_shift =ID_AA64PFR0_AMU_SHIFT , + .ftr_min =ID_AA64PFR0_AMU , + .ftr_signed =FTR_UNSIGNED , + .cfg_reg =VCPU_CPTR_EL2 , + .cfg_mask =CPTR_EL2_TAM , + .cfg_val =CPTR_EL2_TAM , +}; +struct id_reg_info {u32 sys_reg;/* Register ID */ u64 sys_val;/* Sanitized system value */
@@ -847,6 +868,11 @@ static struct id_reg_info id_aa64pfr0_el1_info = { .init = init_id_aa64pfr0_el1_info, .validate = validate_id_aa64pfr0_el1, .get_reset_val = get_reset_id_aa64pfr0_el1, + .trap_features = &(const struct feature_config_ctrl *[]) { + &ftr_ctrl_ras, + &ftr_ctrl_amu, +NULL , + }, };static struct id_reg_info id_aa64pfr1_el1_info = {
@@ -1003,6 +1029,18 @@ static inline bool vcpu_feature_is_available(struct kvm_vcpu *vcpu,return feature_avail (ctrl, val); } +static bool trap_ras_regs (struct kvm_vcpu *vcpu, +struct sys_reg_params *p, +const struct sys_reg_desc *r) +{ +if (!vcpu_feature_is_available (vcpu, &ftr_ctrl_ras)) { +kvm_inject_undefined (vcpu); +return false; + } + +return trap_raz_wi (vcpu, p, r); +} +/* * ARMv8.1 mandates at least a trivial LORegion implementation, where all the * RW registers are RES0 (which we can implement as RAZ/WI). On an ARMv8.0
@@ -2265,14 +2303,14 @@ static const struct sys_reg_desc sys_reg_descs[] = { { SYS_DESC(SYS_AFSR1_EL1), access_vm_reg, reset_unknown, AFSR1_EL1 }, { SYS_DESC(SYS_ESR_EL1), access_vm_reg, reset_unknown, ESR_EL1 }, - { SYS_DESC(SYS_ERRIDR_EL1), trap_raz_wi }, - { SYS_DESC(SYS_ERRSELR_EL1), trap_raz_wi }, - { SYS_DESC(SYS_ERXFR_EL1), trap_raz_wi }, - { SYS_DESC(SYS_ERXCTLR_EL1), trap_raz_wi }, - { SYS_DESC(SYS_ERXSTATUS_EL1), trap_raz_wi }, - { SYS_DESC(SYS_ERXADDR_EL1), trap_raz_wi }, - { SYS_DESC(SYS_ERXMISC0_EL1), trap_raz_wi }, - { SYS_DESC(SYS_ERXMISC1_EL1), trap_raz_wi }, + { SYS_DESC(SYS_ERRIDR_EL1), trap_ras_regs }, + { SYS_DESC(SYS_ERRSELR_EL1), trap_ras_regs }, + { SYS_DESC(SYS_ERXFR_EL1), trap_ras_regs }, + { SYS_DESC(SYS_ERXCTLR_EL1), trap_ras_regs }, + { SYS_DESC(SYS_ERXSTATUS_EL1), trap_ras_regs }, + { SYS_DESC(SYS_ERXADDR_EL1), trap_ras_regs }, + { SYS_DESC(SYS_ERXMISC0_EL1), trap_ras_regs }, + { SYS_DESC(SYS_ERXMISC1_EL1), trap_ras_regs },MTE_REG (TFSR_EL1 ), MTE_REG(TFSRE0_EL1),
Signature · 6 lines
2.33.1.1089.g2158813163f-goog _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
RFC PATCH v2 23/28 KVM: arm64: Trap disabled features of ID_AA64PFR1_EL1
In reply to Reiji WatanabeAdd feature_config_ctrl for MTE, which is indicated in ID_AA64PFR1_EL1, to program configuration register to trap the guest's using the feature when it is not exposed to the guest.
--- arch/arm64/kvm/sys_regs.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+)
arch/arm64/kvm/sys_regs.c +15 -0
@@ -424,6 +424,17 @@ static struct feature_config_ctrl ftr_ctrl_amu = { .cfg_val = CPTR_EL2_TAM, }; +/* For ID_AA64PFR1_EL1 */ +static struct feature_config_ctrl ftr_ctrl_mte = { + .ftr_reg =SYS_ID_AA64PFR1_EL1 , + .ftr_shift =ID_AA64PFR1_MTE_SHIFT , + .ftr_min =ID_AA64PFR1_MTE_EL0 , + .ftr_signed =FTR_UNSIGNED , + .cfg_reg =VCPU_HCR_EL2 , + .cfg_mask = (HCR_TID5 |HCR_DCT |HCR_ATA ), + .cfg_val =HCR_TID5 , +}; +struct id_reg_info {u32 sys_reg;/* Register ID */ u64 sys_val;/* Sanitized system value */
@@ -880,6 +891,10 @@ static struct id_reg_info id_aa64pfr1_el1_info = { .init = init_id_aa64pfr1_el1_info, .validate = validate_id_aa64pfr1_el1, .get_reset_val = get_reset_id_aa64pfr1_el1, + .trap_features = &(const struct feature_config_ctrl *[]) { + &ftr_ctrl_mte, +NULL , + }, };static struct id_reg_info id_aa64isar0_el1_info = {
Signature · 6 lines
2.33.1.1089.g2158813163f-goog _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
RFC PATCH v2 24/28 KVM: arm64: Trap disabled features of ID_AA64DFR0_EL1
In reply to Reiji WatanabeAdd feature_config_ctrl for PMUv3, PMS and TraceFilt, which are indicated in ID_AA64DFR0_EL1, to program configuration registers to trap guest's using those features when they are not exposed to the guest.
--- arch/arm64/kvm/sys_regs.c | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+)
arch/arm64/kvm/sys_regs.c +38 -0
@@ -435,6 +435,38 @@ static struct feature_config_ctrl ftr_ctrl_mte = { .cfg_val = HCR_TID5, }; +/* For ID_AA64DFR0_EL1 */ +static struct feature_config_ctrl ftr_ctrl_pmuv3 = { + .ftr_reg =SYS_ID_AA64DFR0_EL1 , + .ftr_shift =ID_AA64DFR0_PMUVER_SHIFT , + .ftr_min =ID_AA64DFR0_PMUVER_8_0 , + .ftr_signed =FTR_UNSIGNED , + .cfg_reg =VCPU_MDCR_EL2 , + .cfg_mask =MDCR_EL2_TPM , + .cfg_val =MDCR_EL2_TPM , +}; + +static struct feature_config_ctrl ftr_ctrl_pms = { + .ftr_reg =SYS_ID_AA64DFR0_EL1 , + .ftr_shift =ID_AA64DFR0_PMSVER_SHIFT , + .ftr_min =ID_AA64DFR0_PMSVER_8_2 , + .ftr_signed =FTR_UNSIGNED , + .cfg_reg =VCPU_MDCR_EL2 , + .cfg_mask = (MDCR_EL2_TPMS | + (MDCR_EL2_E2PB_MASK <<MDCR_EL2_E2PB_SHIFT )), + .cfg_val =MDCR_EL2_TPMS , +}; + +static struct feature_config_ctrl ftr_ctrl_tracefilt = { + .ftr_reg =SYS_ID_AA64DFR0_EL1 , + .ftr_shift =ID_AA64DFR0_TRACE_FILT_SHIFT , + .ftr_min =1 , + .ftr_signed =FTR_UNSIGNED , + .cfg_reg =VCPU_MDCR_EL2 , + .cfg_mask =MDCR_EL2_TTRF , + .cfg_val =MDCR_EL2_TTRF , +}; +struct id_reg_info {u32 sys_reg;/* Register ID */ u64 sys_val;/* Sanitized system value */
@@ -928,6 +960,12 @@ static struct id_reg_info id_aa64dfr0_el1_info = { .init = init_id_aa64dfr0_el1_info, .validate = validate_id_aa64dfr0_el1, .get_reset_val = get_reset_id_aa64dfr0_el1, + .trap_features = &(const struct feature_config_ctrl *[]) { + &ftr_ctrl_pmuv3, + &ftr_ctrl_pms, + &ftr_ctrl_tracefilt, +NULL , + }, };static struct id_reg_info id_dfr0_el1_info = {
Signature · 6 lines
2.33.1.1089.g2158813163f-goog _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
RFC PATCH v2 25/28 KVM: arm64: Trap disabled features of ID_AA64MMFR1_EL1
In reply to Reiji WatanabeAdd feature_config_ctrl for LORegions, which is indicated in ID_AA64MMFR1_EL1, to program configuration register to trap guest's using the feature when it is not exposed to the guest.
Change trap_loregion() to use vcpu_feature_is_available() to simplify checking of the feature's availability.
--- arch/arm64/kvm/sys_regs.c | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-)
arch/arm64/kvm/sys_regs.c +21 -2
@@ -467,6 +467,17 @@ static struct feature_config_ctrl ftr_ctrl_tracefilt = { .cfg_val = MDCR_EL2_TTRF, }; +/* For ID_AA64MMFR1_EL1 */ +static struct feature_config_ctrl ftr_ctrl_lor = { + .ftr_reg =SYS_ID_AA64MMFR1_EL1 , + .ftr_shift =ID_AA64MMFR1_LOR_SHIFT , + .ftr_min =1 , + .ftr_signed =FTR_UNSIGNED , + .cfg_reg =VCPU_HCR_EL2 , + .cfg_mask =HCR_TLOR , + .cfg_val =HCR_TLOR , +}; +struct id_reg_info {u32 sys_reg;/* Register ID */ u64 sys_val;/* Sanitized system value */
@@ -968,6 +979,14 @@ static struct id_reg_info id_aa64dfr0_el1_info = { }, }; +static struct id_reg_info id_aa64mmfr1_el1_info = { + .sys_reg =SYS_ID_AA64MMFR1_EL1 , + .trap_features = &(const struct feature_config_ctrl *[]) { + &ftr_ctrl_lor, +NULL , + }, +}; +static struct id_reg_info id_dfr0_el1_info = { .sys_reg =SYS_ID_DFR0_EL1 , .init = init_id_dfr0_el1_info,
@@ -1010,6 +1029,7 @@ static struct id_reg_info *id_reg_info_table[KVM_ARM_ID_REG_MAX_NUM] = { [IDREG_IDX(SYS_ID_AA64ISAR0_EL1)] = &id_aa64isar0_el1_info, [IDREG_IDX(SYS_ID_AA64ISAR1_EL1)] = &id_aa64isar1_el1_info, [IDREG_IDX(SYS_ID_AA64MMFR0_EL1)] = &id_aa64mmfr0_el1_info, + [IDREG_IDX(SYS_ID_AA64MMFR1_EL1)] = &id_aa64mmfr1_el1_info, }; static int validate_id_reg(struct kvm_vcpu *vcpu,
@@ -1104,10 +1124,9 @@ static bool trap_loregion(struct kvm_vcpu *vcpu,struct sys_reg_params *p, const struct sys_reg_desc *r) { - u64 val = __vcpu_sys_reg(vcpu, IDREG_SYS_IDX(SYS_ID_AA64MMFR1_EL1)); u32 sr = reg_to_encoding(r); -if (!(val & (0xfUL <<ID_AA64MMFR1_LOR_SHIFT ))) { +if (!vcpu_feature_is_available (vcpu, &ftr_ctrl_lor)) {kvm_inject_undefined (vcpu);return false; }
Signature · 6 lines
2.33.1.1089.g2158813163f-goog _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
RFC PATCH v2 26/28 KVM: arm64: Trap disabled features of ID_AA64ISAR1_EL1
In reply to Reiji WatanabeAdd feature_config_ctrl for PTRAUTH, which is indicated in ID_AA64ISAR1_EL1, to program configuration register to trap guest's using the feature when it is not exposed to the guest.
--- arch/arm64/kvm/sys_regs.c | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+)
arch/arm64/kvm/sys_regs.c +36 -0
@@ -374,6 +374,30 @@ static int arm64_check_features(u64 check_types, u64 val, u64 lim) (cpuid_feature_extract_unsigned_field (val,ID_AA64ISAR1_GPI_SHIFT ) >= \ID_AA64ISAR1_GPI_IMP_DEF ) +/* +* Return true if ptrauth needs to be trapped. +* (i.e. if ptrauth is supported on the host but not exposed to the guest) + */ +static bool vcpu_need_trap_ptrauth (struct kvm_vcpu *vcpu) +{ +u64 val; +bool generic, address; + +if (!system_has_full_ptr_auth ()) +/* The feature is not supported. */ +return false; + + val =__vcpu_sys_reg (vcpu,IDREG_SYS_IDX (SYS_ID_AA64ISAR1_EL1 )); + generic =aa64isar1_has_gpi (val) ||aa64isar1_has_gpa (val); + address =aa64isar1_has_api (val) ||aa64isar1_has_apa (val); +if (generic && address) +/* The feature is available. */ +return false; + +/* The feature is supported but hidden. */ +return true; +} +enum vcpu_config_reg {VCPU_HCR_EL2 =1 ,VCPU_MDCR_EL2 ,
@@ -478,6 +502,14 @@ static struct feature_config_ctrl ftr_ctrl_lor = { .cfg_val = HCR_TLOR, }; +/* For SYS_ID_AA64ISAR1_EL1 */ +static struct feature_config_ctrl ftr_ctrl_ptrauth = { + .ftr_need_trap = vcpu_need_trap_ptrauth, + .cfg_reg =VCPU_HCR_EL2 , + .cfg_mask = (HCR_API |HCR_APK ), + .cfg_val =0 , +}; +struct id_reg_info {u32 sys_reg;/* Register ID */ u64 sys_val;/* Sanitized system value */
@@ -953,6 +985,10 @@ static struct id_reg_info id_aa64isar1_el1_info = { .init = init_id_aa64isar1_el1_info, .validate = validate_id_aa64isar1_el1, .get_reset_val = get_reset_id_aa64isar1_el1, + .trap_features = &(const struct feature_config_ctrl *[]) { + &ftr_ctrl_ptrauth, +NULL , + }, };static struct id_reg_info id_aa64mmfr0_el1_info = {
Signature · 6 lines
2.33.1.1089.g2158813163f-goog _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
RFC PATCH v2 27/28 KVM: arm64: Activate trapping of disabled CPU features for the guest
In reply to Reiji WatanabeCall kvm_vcpu_id_regs_trap_activate() at the first KVM_RUN to activate trapping of disabled CPU features.
--- arch/arm64/include/asm/kvm_host.h | 1 + arch/arm64/kvm/arm.c | 2 ++ 2 files changed, 3 insertions(+)
arch/arm64/include/asm/kvm_host.h +1 -0
@@ -743,6 +743,7 @@ long kvm_vm_ioctl_mte_copy_tags(struct kvm *kvm, struct kvm_arm_copy_mte_tags *copy_tags);int kvm_id_regs_consistency_check (const struct kvm_vcpu *vcpu); +void kvm_vcpu_id_regs_trap_activate (struct kvm_vcpu *vcpu);/* Guest/host FPSIMD coordination helpers */ int kvm_arch_vcpu_run_map_fp (struct kvm_vcpu *vcpu);
arch/arm64/kvm/arm.c +2 -0
@@ -583,6 +583,8 @@ static int kvm_vcpu_first_run_init(struct kvm_vcpu *vcpu)return -EPERM ; } +kvm_vcpu_id_regs_trap_activate (vcpu); +kvm_arm_vcpu_init_debug (vcpu);if (likely (irqchip_in_kernel (kvm))) {
Signature · 6 lines
2.33.1.1089.g2158813163f-goog _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
RFC PATCH v2 28/28 KVM: arm64: selftests: Introduce id_reg_test
In reply to Reiji WatanabeIntroduce a test for aarch64 to validate basic behavior of KVM_GET_ONE_REG and KVM_SET_ONE_REG for ID registers.
This test runs only when KVM_CAP_ARM_ID_REG_WRITABLE is supported.
--- tools/arch/arm64/include/asm/sysreg.h | 1 + tools/testing/selftests/kvm/.gitignore | 1 + tools/testing/selftests/kvm/Makefile | 1 + .../selftests/kvm/aarch64/id_reg_test.c | 1296 +++++++++++++++++ 4 files changed, 1299 insertions(+) create mode 100644 tools/testing/selftests/kvm/aarch64/id_reg_test.c
tools/arch/arm64/include/asm/sysreg.h +1 -0
@@ -793,6 +793,7 @@#define ID_AA64PFR0_ELx_32BIT_64BIT 0x2/* id_aa64pfr1 */ +#define ID_AA64PFR1_CSV2FRAC_SHIFT 32#define ID_AA64PFR1_MPAMFRAC_SHIFT 16#define ID_AA64PFR1_RASFRAC_SHIFT 12#define ID_AA64PFR1_MTE_SHIFT 8
tools/testing/selftests/kvm/.gitignore +1 -0
@@ -2,6 +2,7 @@ /aarch64/arch_timer /aarch64/debug-exceptions /aarch64/get-reg-list +/aarch64/id_reg_test /aarch64/psci_cpu_on_test /aarch64/vgic_init /s390x/memop
tools/testing/selftests/kvm/Makefile +1 -0
@@ -89,6 +89,7 @@ TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_aarch64 += aarch64/arch_timer TEST_GEN_PROGS_aarch64 += aarch64/debug-exceptions TEST_GEN_PROGS_aarch64 += aarch64/get-reg-list +TEST_GEN_PROGS_aarch64 += aarch64/id_reg_test TEST_GEN_PROGS_aarch64 += aarch64/psci_cpu_on_test TEST_GEN_PROGS_aarch64 += aarch64/vgic_init TEST_GEN_PROGS_aarch64 += demand_paging_test
tools/testing/selftests/kvm/aarch64/id_reg_test.c new file +1296 -0
1,296 lines not on this page · raw message
Signature · 1 line
2.33.1.1089.g2158813163f-goog