KVM/ARM: Some vgic fixes and init sequence KVM selftests
Subsystems (5)
v5 cover KVM/ARM: Some vgic fixes and init sequence KVM selftests
While writting vgic v3 init sequence KVM selftests I noticed some relatively minor issues. This was also the opportunity to try to fix the issue laterly reported by Zenghui, related to the RDIST_TYPER last bit emulation. The final patch is a first batch of VGIC init sequence selftests. Of course they can be augmented with a lot more register access tests, but let's try to move forward incrementally ...
Best Regards
Eric
This series can be found at:
https://github.com/eauger/linux/tree/vgic_kvmselftests_v5
History:
v4 -> v5:
- rewrite the last bit detection according to Marc's interpretation of the spec and modify the kvm selftests accordingly
v3 -> v4:
- take into account Drew's comment on the kvm selftests. No change to the KVM related patches compared to v3
v2 ->v3:
- reworked last bit read accessor to handle contiguous redist regions and rdist not registered in ascending order
- removed [PATCH 5/9] KVM: arm: move has_run_once after the map_resources
v1 -> v2:
- Took into account all comments from Marc and Alexandru's except the has_run_once still after the map_resources (this would oblige me to revisit in depth the selftests)
Eric Auger (8):
KVM: arm64: Fix KVM_VGIC_V3_ADDR_TYPE_REDIST_REGION read
KVM: arm64: vgic-v3: Fix error handling in vgic_v3_set_redist_base()
KVM: arm/arm64: vgic: Reset base address on kvm_vgic_dist_destroy()
docs: kvm: devices/arm-vgic-v3: enhance KVM_DEV_ARM_VGIC_CTRL_INIT doc
KVM: arm64: Simplify argument passing to vgic_uaccess_[read|write]
kvm: arm64: vgic-v3: Introduce vgic_v3_free_redist_region()
KVM: arm64: vgic-v3: Expose GICR_TYPER.Last for userspace
KVM: selftests: aarch64/vgic-v3 init sequence tests
.../virt/kvm/devices/arm-vgic-v3.rst | 2 +- arch/arm64/kvm/vgic/vgic-init.c | 12 +- arch/arm64/kvm/vgic/vgic-kvm-device.c | 3 + arch/arm64/kvm/vgic/vgic-mmio-v3.c | 79 ++- arch/arm64/kvm/vgic/vgic-mmio.c | 10 +- arch/arm64/kvm/vgic/vgic.h | 1 + include/kvm/arm_vgic.h | 1 + tools/testing/selftests/kvm/.gitignore | 1 + tools/testing/selftests/kvm/Makefile | 1 + .../testing/selftests/kvm/aarch64/vgic_init.c | 585 ++++++++++++++++++ .../testing/selftests/kvm/include/kvm_util.h | 9 + tools/testing/selftests/kvm/lib/kvm_util.c | 77 +++ 12 files changed, 739 insertions(+), 42 deletions(-) create mode 100644 tools/testing/selftests/kvm/aarch64/vgic_init.c
Signature · 6 lines
2.26.3 _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
PATCH v5 1/8 KVM: arm64: Fix KVM_VGIC_V3_ADDR_TYPE_REDIST_REGION read
The doc says:
"The characteristics of a specific redistributor region can
be read by presetting the index field in the attr data. Only valid for KVM_DEV_TYPE_ARM_VGIC_V3"
Unfortunately the existing code fails to read the input attr data.
---
v1 -> v2:
- in the commit message, remove the statement that the index always is 0
- add Alexandru's R-b
--- arch/arm64/kvm/vgic/vgic-kvm-device.c | 3 +++ 1 file changed, 3 insertions(+)
arch/arm64/kvm/vgic/vgic-kvm-device.c +3 -0
@@ -226,6 +226,9 @@ static int vgic_get_common_attr(struct kvm_device *dev,u64 addr;unsigned long type = (unsigned long )attr->attr; +if (copy_from_user (&addr, uaddr,sizeof (addr))) +return -EFAULT ; + r =kvm_vgic_addr (dev->kvm, type, &addr, false);if (r)return (r == -ENODEV ) ? -ENXIO : r;
Signature · 6 lines
2.26.3 _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
PATCH v5 2/8 KVM: arm64: vgic-v3: Fix error handling in vgic_v3_set_redist_base()
In reply to Eric Augervgic_v3_insert_redist_region() may succeed while vgic_register_all_redist_iodevs fails. For example this happens while adding a redistributor region overlapping a dist region. The failure only is detected on vgic_register_all_redist_iodevs when vgic_v3_check_base() gets called in vgic_register_redist_iodev().
In such a case, remove the newly added redistributor region and free it.
---
v1 -> v2:
- fix the commit message and split declaration/assignment of rdreg
--- arch/arm64/kvm/vgic/vgic-mmio-v3.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
arch/arm64/kvm/vgic/vgic-mmio-v3.c +7 -1
@@ -861,8 +861,14 @@ int vgic_v3_set_redist_base(struct kvm *kvm, u32 index, u64 addr, u32 count)* afterwards will register the iodevs when needed. */ ret =vgic_register_all_redist_iodevs (kvm); -if (ret) +if (ret) { +struct vgic_redist_region *rdreg; + + rdreg =vgic_v3_rdist_region_from_index (kvm, index); +list_del (&rdreg->list); +kfree (rdreg);return ret; + }return 0 ; }
Signature · 6 lines
2.26.3 _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
PATCH v5 3/8 KVM: arm/arm64: vgic: Reset base address on kvm_vgic_dist_destroy()
In reply to Eric AugerOn vgic_dist_destroy(), the addresses are not reset. However for kvm selftest purpose this would allow to continue the test execution even after a failure when running KVM_RUN. So let's reset the base addresses.
---
v1 -> v2:
- use dist-> in the else and add braces
--- arch/arm64/kvm/vgic/vgic-init.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
arch/arm64/kvm/vgic/vgic-init.c +5 -1
@@ -335,13 +335,16 @@ static void kvm_vgic_dist_destroy(struct kvm *kvm)kfree (dist->spis); dist->spis =NULL ; dist->nr_spis =0 ; + dist->vgic_dist_base =VGIC_ADDR_UNDEF ; -if (kvm->arch.vgic.vgic_model ==KVM_DEV_TYPE_ARM_VGIC_V3 ) { +if (dist->vgic_model ==KVM_DEV_TYPE_ARM_VGIC_V3 ) {list_for_each_entry_safe (rdreg, next, &dist->rd_regions, list) {list_del (&rdreg->list);kfree (rdreg); }INIT_LIST_HEAD (&dist->rd_regions); + }else { + dist->vgic_cpu_base =VGIC_ADDR_UNDEF ; }if (vgic_has_its (kvm))
@@ -362,6 +365,7 @@ void kvm_vgic_vcpu_destroy(struct kvm_vcpu *vcpu)vgic_flush_pending_lpis (vcpu);INIT_LIST_HEAD (&vgic_cpu->ap_list_head); + vgic_cpu->rd_iodev.base_addr =VGIC_ADDR_UNDEF ; }/* To be called with kvm->lock held */
Signature · 1 line
2.26.3
PATCH v5 4/8 docs: kvm: devices/arm-vgic-v3: enhance KVM_DEV_ARM_VGIC_CTRL_INIT doc
In reply to Eric Augerkvm_arch_vcpu_precreate() returns -EBUSY if the vgic is already initialized. So let's document that KVM_DEV_ARM_VGIC_CTRL_INIT must be called after all vcpu creations.
---
v1 -> v2:
- Must be called after all vcpu creations -> Must be called after all VCPUs have been created as per Alexandru's suggestion
--- Documentation/virt/kvm/devices/arm-vgic-v3.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/virt/kvm/devices/arm-vgic-v3.rst +1 -1
@@ -228,7 +228,7 @@ Groups: KVM_DEV_ARM_VGIC_CTRL_INIT request the initialization of the VGIC, no additional parameter in - kvm_device_attr.addr. + kvm_device_attr.addr. Must be called after all VCPUs have been created. KVM_DEV_ARM_VGIC_SAVE_PENDING_TABLES save all LPI pending bits into guest RAM pending tables.
Signature · 6 lines
2.26.3 _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
PATCH v5 5/8 KVM: arm64: Simplify argument passing to vgic_uaccess_[read|write]
In reply to Eric Augervgic_uaccess() takes a struct vgic_io_device argument, converts it to a struct kvm_io_device and passes it to the read/write accessor functions, which convert it back to a struct vgic_io_device. Avoid the indirection by passing the struct vgic_io_device argument directly to vgic_uaccess_{read,write}.
---
v1 -> v2:
- reworded the commit message as suggested by Alexandru
--- arch/arm64/kvm/vgic/vgic-mmio.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)
arch/arm64/kvm/vgic/vgic-mmio.c +4 -6
@@ -938,10 +938,9 @@ vgic_get_mmio_region(struct kvm_vcpu *vcpu, struct vgic_io_device *iodev,return region; } -static int vgic_uaccess_read (struct kvm_vcpu *vcpu,struct kvm_io_device *dev, +static int vgic_uaccess_read (struct kvm_vcpu *vcpu,struct vgic_io_device *iodev,gpa_t addr,u32 *val) { -struct vgic_io_device *iodev =kvm_to_vgic_iodev (dev);const struct vgic_register_region *region;struct kvm_vcpu *r_vcpu;
@@ -960,10 +959,9 @@ static int vgic_uaccess_read(struct kvm_vcpu *vcpu, struct kvm_io_device *dev,return 0 ; } -static int vgic_uaccess_write (struct kvm_vcpu *vcpu,struct kvm_io_device *dev, +static int vgic_uaccess_write (struct kvm_vcpu *vcpu,struct vgic_io_device *iodev,gpa_t addr,const u32 *val) { -struct vgic_io_device *iodev =kvm_to_vgic_iodev (dev);const struct vgic_register_region *region;struct kvm_vcpu *r_vcpu;
@@ -986,9 +984,9 @@ int vgic_uaccess(struct kvm_vcpu *vcpu, struct vgic_io_device *dev, bool is_write, int offset, u32 *val) { if (is_write) - return vgic_uaccess_write(vcpu, &dev->dev, offset, val); + return vgic_uaccess_write(vcpu, dev, offset, val); else - return vgic_uaccess_read(vcpu, &dev->dev, offset, val); + return vgic_uaccess_read(vcpu, dev, offset, val); } static int dispatch_mmio_read(struct kvm_vcpu *vcpu, struct kvm_io_device *dev,
Signature · 6 lines
2.26.3 _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
PATCH v5 6/8 kvm: arm64: vgic-v3: Introduce vgic_v3_free_redist_region()
In reply to Eric AugerTo improve the readability, we introduce the new vgic_v3_free_redist_region helper and also rename vgic_v3_insert_redist_region into vgic_v3_alloc_redist_region
--- arch/arm64/kvm/vgic/vgic-init.c | 6 ++---- arch/arm64/kvm/vgic/vgic-mmio-v3.c | 17 +++++++++++------ arch/arm64/kvm/vgic/vgic.h | 1 + 3 files changed, 14 insertions(+), 10 deletions(-)
arch/arm64/kvm/vgic/vgic-init.c +2 -4
@@ -338,10 +338,8 @@ static void kvm_vgic_dist_destroy(struct kvm *kvm) dist->vgic_dist_base =VGIC_ADDR_UNDEF ;if (dist->vgic_model ==KVM_DEV_TYPE_ARM_VGIC_V3 ) { -list_for_each_entry_safe (rdreg, next, &dist->rd_regions, list) { -list_del (&rdreg->list); -kfree (rdreg); - } +list_for_each_entry_safe (rdreg, next, &dist->rd_regions, list) +vgic_v3_free_redist_region (rdreg);INIT_LIST_HEAD (&dist->rd_regions); }else { dist->vgic_cpu_base =VGIC_ADDR_UNDEF ;
arch/arm64/kvm/vgic/vgic-mmio-v3.c +11 -6
@@ -768,7 +768,7 @@ static int vgic_register_all_redist_iodevs(struct kvm *kvm) }/** -* vgic_v3_insert_redist_region - Insert a new redistributor region +* vgic_v3_alloc_redist_region - Allocate a new redistributor region * * Performs various checks before inserting the rdist region in the list. * Those tests depend on whether the size of the rdist region is known
@@ -782,8 +782,8 @@ static int vgic_register_all_redist_iodevs(struct kvm *kvm)* * Return 0 on success, < 0 otherwise */ -static int vgic_v3_insert_redist_region (struct kvm *kvm,uint32_t index, -gpa_t base,uint32_t count) +static int vgic_v3_alloc_redist_region (struct kvm *kvm,uint32_t index, +gpa_t base,uint32_t count) {struct vgic_dist *d = &kvm->arch.vgic;struct vgic_redist_region *rdreg;
@@ -848,11 +848,17 @@ static int vgic_v3_insert_redist_region(struct kvm *kvm, uint32_t index,return ret; } +void vgic_v3_free_redist_region (struct vgic_redist_region *rdreg) +{ +list_del (&rdreg->list); +kfree (rdreg); +} +int vgic_v3_set_redist_base (struct kvm *kvm,u32 index,u64 addr,u32 count) {int ret; - ret =vgic_v3_insert_redist_region (kvm, index, addr, count); + ret =vgic_v3_alloc_redist_region (kvm, index, addr, count);if (ret)return ret;
@@ -865,8 +871,7 @@ int vgic_v3_set_redist_base(struct kvm *kvm, u32 index, u64 addr, u32 count)struct vgic_redist_region *rdreg; rdreg =vgic_v3_rdist_region_from_index (kvm, index); -list_del (&rdreg->list); -kfree (rdreg); +vgic_v3_free_redist_region (rdreg);return ret; }
arch/arm64/kvm/vgic/vgic.h +1 -0
@@ -293,6 +293,7 @@ vgic_v3_rd_region_size(struct kvm *kvm, struct vgic_redist_region *rdreg)struct vgic_redist_region *vgic_v3_rdist_region_from_index (struct kvm *kvm,u32 index); +void vgic_v3_free_redist_region (struct vgic_redist_region *rdreg);bool vgic_v3_rdist_overlap (struct kvm *kvm,gpa_t base,size_t size);
Signature · 6 lines
2.26.3 _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
PATCH v5 7/8 KVM: arm64: vgic-v3: Expose GICR_TYPER.Last for userspace
In reply to Eric AugerCommit 23bde34771f1 ("KVM: arm64: vgic-v3: Drop the reporting of GICR_TYPER.Last for userspace") temporarily fixed a bug identified when attempting to access the GICR_TYPER register before the redistributor region setting, but dropped the support of the LAST bit.
Emulating the GICR_TYPER.Last bit still makes sense for architecture compliance though. This patch restores its support (if the redistributor region was set) while keeping the code safe.
We introduce a new helper, vgic_mmio_vcpu_rdist_is_last() which computes whether a redistributor is the highest one of a series of redistributor contributor pages.
With this new implementation we do not need to have a uaccess read accessor anymore.
---
v4 -> v5:
- redist region list now is sorted by @base
- change the implementation according to Marc's understanding of the spec
--- arch/arm64/kvm/vgic/vgic-mmio-v3.c | 58 +++++++++++++++++------------- include/kvm/arm_vgic.h | 1 + 2 files changed, 34 insertions(+), 25 deletions(-)
arch/arm64/kvm/vgic/vgic-mmio-v3.c +33 -25
@@ -251,45 +251,52 @@ static void vgic_mmio_write_v3r_ctlr(struct kvm_vcpu *vcpu,vgic_enable_lpis (vcpu); } +static bool vgic_mmio_vcpu_rdist_is_last (struct kvm_vcpu *vcpu) +{ +struct vgic_dist *vgic = &vcpu->kvm->arch.vgic; +struct vgic_cpu *vgic_cpu = &vcpu->arch.vgic_cpu; +struct vgic_redist_region *iter, *rdreg = vgic_cpu->rdreg; + +if (!rdreg) +return false; + +if (vgic_cpu->rdreg_index < rdreg->free_index -1 ) { +return false; + }else if (rdreg->count && vgic_cpu->rdreg_index == (rdreg->count -1 )) { +struct list_head *rd_regions = &vgic->rd_regions; +gpa_t end = rdreg->base + rdreg->count *KVM_VGIC_V3_REDIST_SIZE ; + +/* +* the rdist is the last one of the redist region, +* check whether there is no other contiguous rdist region +*/ +list_for_each_entry (iter, rd_regions, list) { +if (iter->base == end && iter->free_index >0 ) +return false; + } + } +return true; +} +static unsigned long vgic_mmio_read_v3r_typer (struct kvm_vcpu *vcpu,gpa_t addr,unsigned int len) {unsigned long mpidr =kvm_vcpu_get_mpidr_aff (vcpu); -struct vgic_cpu *vgic_cpu = &vcpu->arch.vgic_cpu; -struct vgic_redist_region *rdreg = vgic_cpu->rdreg;int target_vcpu_id = vcpu->vcpu_id; -gpa_t last_rdist_typer = rdreg->base +GICR_TYPER + - (rdreg->free_index -1 ) *KVM_VGIC_V3_REDIST_SIZE ;u64 value; value = (u64)(mpidr &GENMASK (23 ,0 )) <<32 ; value |= ((target_vcpu_id &0xffff ) <<8 ); -if (addr == last_rdist_typer) +if (vgic_has_its (vcpu->kvm)) + value |=GICR_TYPER_PLPIS ; + +if (vgic_mmio_vcpu_rdist_is_last (vcpu)) value |=GICR_TYPER_LAST ; -if (vgic_has_its (vcpu->kvm)) - value |=GICR_TYPER_PLPIS ;return extract_bytes (value, addr &7 , len); } -static unsigned long vgic_uaccess_read_v3r_typer (struct kvm_vcpu *vcpu, -gpa_t addr,unsigned int len) -{ -unsigned long mpidr =kvm_vcpu_get_mpidr_aff (vcpu); -int target_vcpu_id = vcpu->vcpu_id; -u64 value; - - value = (u64)(mpidr &GENMASK (23 ,0 )) <<32 ; - value |= ((target_vcpu_id &0xffff ) <<8 ); - -if (vgic_has_its (vcpu->kvm)) - value |=GICR_TYPER_PLPIS ; - -/* reporting of the Last bit is not supported for userspace */ -return extract_bytes (value, addr &7 , len); -} -static unsigned long vgic_mmio_read_v3r_iidr (struct kvm_vcpu *vcpu,gpa_t addr,unsigned int len) {
@@ -612,7 +619,7 @@ static const struct vgic_register_region vgic_v3_rd_registers[] = { VGIC_ACCESS_32bit),REGISTER_DESC_WITH_LENGTH_UACCESS (GICR_TYPER , vgic_mmio_read_v3r_typer, vgic_mmio_write_wi, - vgic_uaccess_read_v3r_typer, vgic_mmio_uaccess_write_wi,8 , +NULL , vgic_mmio_uaccess_write_wi,8 , VGIC_ACCESS_64bit | VGIC_ACCESS_32bit), REGISTER_DESC_WITH_LENGTH(GICR_WAKER, vgic_mmio_read_raz, vgic_mmio_write_wi, 4,
@@ -714,6 +721,7 @@ int vgic_register_redist_iodev(struct kvm_vcpu *vcpu)return -EINVAL ; vgic_cpu->rdreg = rdreg; + vgic_cpu->rdreg_index = rdreg->free_index; rd_base = rdreg->base + rdreg->free_index *KVM_VGIC_V3_REDIST_SIZE ;
include/kvm/arm_vgic.h +1 -0
@@ -322,6 +322,7 @@ struct vgic_cpu {*/ struct vgic_io_device rd_iodev;struct vgic_redist_region *rdreg; +u32 rdreg_index;/* Contains the attributes and gpa of the LPI pending tables. */ u64 pendbaser;
Signature · 6 lines
2.26.3 _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
Marc Zyngier
maintainerRe: [PATCH v5 7/8] KVM: arm64: vgic-v3: Expose GICR_TYPER.Last for userspace
Quoted 52 lines · Eric Auger
Commit
23bde34771f1("KVM: arm64: vgic-v3: Drop the reporting of GICR_TYPER.Last for userspace") temporarily fixed a bug identified when attempting to access theGICR_TYPERregister before the redistributor region setting, but dropped the support of the LAST bit.Emulating the GICR_TYPER.Last bit still makes sense for architecture compliance though. This patch restores its support (if the redistributor region was set) while keeping the code safe.
We introduce a new helper,
vgic_mmio_vcpu_rdist_is_last()which computes whether a redistributor is the highest one of a series of redistributor contributor pages.With this new implementation we do not need to have a uaccess read accessor anymore.
Signed-off-by Eric Auger <[email protected]>---
v4 -> v5:
- redist region list now is sorted by @base
- change the implementation according to Marc's understanding of the spec--- arch/arm64/kvm/vgic/vgic-mmio-v3.c | 58 +++++++++++++++++------------- include/kvm/arm_vgic.h | 1 + 2 files changed, 34 insertions(+), 25 deletions(-)arch/arm64/kvm/vgic/vgic-mmio-v3.c +13
-0@@ -251,45 +251,52 @@ static void vgic_mmio_write_v3r_ctlr(struct kvm_vcpu *vcpu,vgic_enable_lpis (vcpu); } +static bool vgic_mmio_vcpu_rdist_is_last (struct kvm_vcpu *vcpu) +{ +struct vgic_dist *vgic = &vcpu->kvm->arch.vgic; +struct vgic_cpu *vgic_cpu = &vcpu->arch.vgic_cpu; +struct vgic_redist_region *iter, *rdreg = vgic_cpu->rdreg; + +if (!rdreg) +return false; + +if (vgic_cpu->rdreg_index < rdreg->free_index -1 ) { +return false; + }else if (rdreg->count && vgic_cpu->rdreg_index == (rdreg->count -1 )) { +struct list_head *rd_regions = &vgic->rd_regions;
arch/arm64/kvm/vgic/vgic-mmio-v3.c static void vgic_mmio_write_v3r_ctlr(struct kvm_vcpu *vcpu, · line 276
Quoted 10 lines
arch/arm64/kvm/vgic/vgic-mmio-v3.c +10
-0+gpa_t end = rdreg->base + rdreg->count *KVM_VGIC_V3_REDIST_SIZE ; + +/* +* the rdist is the last one of the redist region, +* check whether there is no other contiguous rdist region +*/ +list_for_each_entry (iter, rd_regions, list) { +if (iter->base == end && iter->free_index >0 ) +return false; + }
In the above notes, you state that the region list is now sorted by base address, but I really can't see what sorts that list. And the lines above indicate that you are still iterating over the whole RD regions.
It's not a big deal (the code is now simple enough), but that's just to confirm that I understand what is going on here.
Thanks,
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Re: [PATCH v5 7/8] KVM: arm64: vgic-v3: Expose GICR_TYPER.Last for userspace
Hi Marc,
Quoted 70 lines · Marc Zyngier
Quoted 52 lines · Eric Auger
Commit
23bde34771f1("KVM: arm64: vgic-v3: Drop the reporting of GICR_TYPER.Last for userspace") temporarily fixed a bug identified when attempting to access theGICR_TYPERregister before the redistributor region setting, but dropped the support of the LAST bit.Emulating the GICR_TYPER.Last bit still makes sense for architecture compliance though. This patch restores its support (if the redistributor region was set) while keeping the code safe.
We introduce a new helper,
vgic_mmio_vcpu_rdist_is_last()which computes whether a redistributor is the highest one of a series of redistributor contributor pages.With this new implementation we do not need to have a uaccess read accessor anymore.
Signed-off-by Eric Auger <[email protected]>---
v4 -> v5:
- redist region list now is sorted by @base
- change the implementation according to Marc's understanding of the spec--- arch/arm64/kvm/vgic/vgic-mmio-v3.c | 58 +++++++++++++++++------------- include/kvm/arm_vgic.h | 1 + 2 files changed, 34 insertions(+), 25 deletions(-)arch/arm64/kvm/vgic/vgic-mmio-v3.c +13
-0@@ -251,45 +251,52 @@ static void vgic_mmio_write_v3r_ctlr(struct kvm_vcpu *vcpu,vgic_enable_lpis (vcpu); } +static bool vgic_mmio_vcpu_rdist_is_last (struct kvm_vcpu *vcpu) +{ +struct vgic_dist *vgic = &vcpu->kvm->arch.vgic; +struct vgic_cpu *vgic_cpu = &vcpu->arch.vgic_cpu; +struct vgic_redist_region *iter, *rdreg = vgic_cpu->rdreg; + +if (!rdreg) +return false; + +if (vgic_cpu->rdreg_index < rdreg->free_index -1 ) { +return false; + }else if (rdreg->count && vgic_cpu->rdreg_index == (rdreg->count -1 )) { +struct list_head *rd_regions = &vgic->rd_regions;arch/arm64/kvm/vgic/vgic-mmio-v3.c static void vgic_mmio_write_v3r_ctlr(struct kvm_vcpu *vcpu, · line 276
Quoted 10 lines
arch/arm64/kvm/vgic/vgic-mmio-v3.c +10
-0+gpa_t end = rdreg->base + rdreg->count *KVM_VGIC_V3_REDIST_SIZE ; + +/* +* the rdist is the last one of the redist region, +* check whether there is no other contiguous rdist region +*/ +list_for_each_entry (iter, rd_regions, list) { +if (iter->base == end && iter->free_index >0 ) +return false; + }In the above notes, you state that the region list is now sorted by base address, but I really can't see what sorts that list. And the lines above indicate that you are still iterating over the whole RD regions.
Quoted 2 lines
It's not a big deal (the code is now simple enough), but that's just to confirm that I understand what is going on here.
Sorry I should have removed the notes. I made the change but then I noticed that the list was already sorted by redistributor region index as the API forbids to register rdist regions in non ascending index order. So sorting by base address was eventually causing more trouble than it helped.
Thanks
Eric
Quoted 5 lines
Thanks,
M.
PATCH v5 8/8 KVM: selftests: aarch64/vgic-v3 init sequence tests
In reply to Eric AugerThe tests exercise the VGIC_V3 device creation including the associated KVM_DEV_ARM_VGIC_GRP_ADDR group attributes:
- KVM_VGIC_V3_ADDR_TYPE_DIST/REDIST
- KVM_VGIC_V3_ADDR_TYPE_REDIST_REGION
Some other tests dedicate to KVM_DEV_ARM_VGIC_GRP_REDIST_REGS group and especially the GICR_TYPER read. The goal was to test the case recently fixed by commit 23bde34771f1
("KVM: arm64: vgic-v3: Drop the reporting of GICR_TYPER.Last for userspace").
The API under test can be found atDocumentation/virt/kvm/devices/arm-vgic-v3.rst
---
v4 -> v5:
- simplify the last bit tests given the simpler interpretation of the spec
v3 -> v4:
- update .gitignore
- More vgic-mmio-v3.c change into the previous patch
- rename fuzz_dist_rdist into test_dist_rdist
- cleanup in run_vcpu and guest_code
- max_ipa_bits is global
- s/fuzz/subtest
- added test_kvm_device,
- moved ucall_init() just before the cpu run
- use vm_create_default_with_vcpus
- use vm_gic struct, vm_gic_create, vm_gic_destroy
- revwrite util.c helpers to comply with the usual style
--- tools/testing/selftests/kvm/.gitignore | 1 + tools/testing/selftests/kvm/Makefile | 1 + .../testing/selftests/kvm/aarch64/vgic_init.c | 585 ++++++++++++++++++ .../testing/selftests/kvm/include/kvm_util.h | 9 + tools/testing/selftests/kvm/lib/kvm_util.c | 77 +++ 5 files changed, 673 insertions(+) create mode 100644 tools/testing/selftests/kvm/aarch64/vgic_init.c
tools/testing/selftests/kvm/.gitignore +1 -0
@@ -1,6 +1,7 @@ # SPDX-License-Identifier: GPL-2.0-only /aarch64/get-reg-list /aarch64/get-reg-list-sve +/aarch64/vgic_init /s390x/memop /s390x/resets /s390x/sync_regs_test
tools/testing/selftests/kvm/Makefile +1 -0
@@ -78,6 +78,7 @@ TEST_GEN_PROGS_x86_64 += steal_time TEST_GEN_PROGS_aarch64 += aarch64/get-reg-list TEST_GEN_PROGS_aarch64 += aarch64/get-reg-list-sve +TEST_GEN_PROGS_aarch64 += aarch64/vgic_init TEST_GEN_PROGS_aarch64 += demand_paging_test TEST_GEN_PROGS_aarch64 += dirty_log_test TEST_GEN_PROGS_aarch64 += dirty_log_perf_test
tools/testing/selftests/kvm/aarch64/vgic_init.c new file +585 -0
585 lines not on this page · raw message
tools/testing/selftests/kvm/include/kvm_util.h +9 -0
@@ -225,6 +225,15 @@ int vcpu_nested_state_set(struct kvm_vm *vm, uint32_t vcpuid,#endif void *vcpu_map_dirty_ring (struct kvm_vm *vm,uint32_t vcpuid); +int _kvm_device_check_attr (int dev_fd,uint32_t group,uint64_t attr); +int kvm_device_check_attr (int dev_fd,uint32_t group,uint64_t attr); +int _kvm_create_device (struct kvm_vm *vm,uint64_t type,bool test); +int kvm_create_device (struct kvm_vm *vm,uint64_t type,bool test); +int _kvm_device_access (int dev_fd,uint32_t group,uint64_t attr, +void *val,bool write); +int kvm_device_access (int dev_fd,uint32_t group,uint64_t attr, +void *val,bool write); +const char *exit_reason_str (unsigned int exit_reason);void virt_pgd_alloc (struct kvm_vm *vm,uint32_t pgd_memslot);
tools/testing/selftests/kvm/lib/kvm_util.c +77 -0
83 lines not on this page · raw message
Signature · 6 lines
2.26.3 _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
Marc Zyngier
maintainerHi Eric,
Quoted 12 lines · Eric Auger
While writting vgic v3 init sequence KVM selftests I noticed some relatively minor issues. This was also the opportunity to try to fix the issue laterly reported by Zenghui, related to the
RDIST_TYPERlast bit emulation. The final patch is a first batch of VGIC init sequence selftests. Of course they can be augmented with a lot more register access tests, but let's try to move forward incrementally ...Best Regards
Eric
Quoted 8 lines
This series can be found at:
https://github.com/eauger/linux/tree/vgic_kvmselftests_v5History:
v4 -> v5:
- rewrite the last bit detection according to Marc's interpretation of the spec and modify the kvm selftests accordingly
Have you dropped v4's patch #1? It did seem to fix an actual issue, didn't it?
Thanks,
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Hi Marc,
Quoted 19 lines · Marc Zyngier
Hi Eric,
Quoted 15 lines · Eric Auger
While writting vgic v3 init sequence KVM selftests I noticed some relatively minor issues. This was also the opportunity to try to fix the issue laterly reported by Zenghui, related to the
RDIST_TYPERlast bit emulation. The final patch is a first batch of VGIC init sequence selftests. Of course they can be augmented with a lot more register access tests, but let's try to move forward incrementally ...Best Regards
Eric
This series can be found at:
https://github.com/eauger/linux/tree/vgic_kvmselftests_v5
Quoted 8 lines
Quoted 5 lines
History:
v4 -> v5:
- rewrite the last bit detection according to Marc's interpretation of the spec and modify the kvm selftests accordinglyHave you dropped v4's patch #1? It did seem to fix an actual issue, didn't it?
Hum no that was not my intent :-( Resending ...
Eric
Quoted 5 lines
Thanks,
M.