irqchip/gic-v4.1: Optimize the wait for the completion of the analysis of the VPT
Subsystems (5)
PATCH 1/1 irqchip/gic-v4.1: Optimize the wait for the completion of the analysis of the VPT
Right after a vPE is made resident, the code starts polling the GICR_VPENDBASER.Dirty bit until it becomes 0, where the delay_us is set to 10. But in our measurement, it takes only hundreds of nanoseconds, or 1~2 microseconds, to finish parsing the VPT in most cases. And we also measured the time from vcpu_load() (include it) to __guest_enter() on Kunpeng 920. On average, it takes 2.55 microseconds (not first run && the VPT is empty). So 10 microseconds delay might really hurt performance.
To avoid this, we can set the delay_us to 1, which is more appropriate in this situation and universal. Besides, we can delay the execution of its_wait_vpt_parse_complete() (call it from kvm_vgic_flush_hwstate() corresponding to vPE resident), giving the GIC a chance to work in parallel with the CPU on the entry path.
--- arch/arm64/kvm/vgic/vgic-v4.c | 18 ++++++++++++++++++ arch/arm64/kvm/vgic/vgic.c | 2 ++ drivers/irqchip/irq-gic-v3-its.c | 14 +++++++++++--- drivers/irqchip/irq-gic-v4.c | 11 +++++++++++ include/kvm/arm_vgic.h | 3 +++ include/linux/irqchip/arm-gic-v4.h | 4 ++++ 6 files changed, 49 insertions(+), 3 deletions(-)
arch/arm64/kvm/vgic/vgic-v4.c +18 -0
@@ -353,6 +353,24 @@ int vgic_v4_load(struct kvm_vcpu *vcpu)return err; } +void vgic_v4_wait_vpt (struct kvm_vcpu *vcpu) +{ +struct its_vpe *vpe; + +if (kvm_vgic_global_state.type ==VGIC_V2 || !vgic_supports_direct_msis (vcpu->kvm)) +return ; + + vpe = &vcpu->arch.vgic_cpu.vgic_v3.its_vpe; + +if (vpe->vpt_ready) +return ; + +if (its_wait_vpt (vpe)) +return ; + + vpe->vpt_ready = true; +} +static struct vgic_its *vgic_get_its (struct kvm *kvm,struct kvm_kernel_irq_routing_entry *irq_entry) {
arch/arm64/kvm/vgic/vgic.c +2 -0
@@ -915,6 +915,8 @@ void kvm_vgic_flush_hwstate(struct kvm_vcpu *vcpu)if (can_access_vgic_from_kernel ())vgic_restore_state (vcpu); + +vgic_v4_wait_vpt (vcpu); }void kvm_vgic_load (struct kvm_vcpu *vcpu)
drivers/irqchip/irq-gic-v3-its.c +11 -3
@@ -3803,7 +3803,7 @@ static void its_wait_vpt_parse_complete(void)WARN_ON_ONCE (readq_relaxed_poll_timeout_atomic (vlpi_base +GICR_VPENDBASER , val, !(val & GICR_VPENDBASER_Dirty), -10 ,500 )); +1 ,500 )); }static void its_vpe_schedule (struct its_vpe *vpe)
@@ -3837,7 +3837,7 @@ static void its_vpe_schedule(struct its_vpe *vpe) val |= GICR_VPENDBASER_Valid;gicr_write_vpendbaser (val, vlpi_base +GICR_VPENDBASER ); -its_wait_vpt_parse_complete (); + vpe->vpt_ready = false; }static void its_vpe_deschedule (struct its_vpe *vpe)
@@ -3881,6 +3881,10 @@ static int its_vpe_set_vcpu_affinity(struct irq_data *d, void *vcpu_info)its_vpe_schedule (vpe);return 0 ; +case WAIT_VPT : +its_wait_vpt_parse_complete (); +return 0 ; +case DESCHEDULE_VPE :its_vpe_deschedule (vpe);return 0 ;
@@ -4047,7 +4051,7 @@ static void its_vpe_4_1_schedule(struct its_vpe *vpe,gicr_write_vpendbaser (val, vlpi_base +GICR_VPENDBASER ); -its_wait_vpt_parse_complete (); + vpe->vpt_ready = false; } static void its_vpe_4_1_deschedule(struct its_vpe *vpe,
@@ -4118,6 +4122,10 @@ static int its_vpe_4_1_set_vcpu_affinity(struct irq_data *d, void *vcpu_info)its_vpe_4_1_schedule (vpe, info);return 0 ; +case WAIT_VPT : +its_wait_vpt_parse_complete (); +return 0 ; +case DESCHEDULE_VPE :its_vpe_4_1_deschedule (vpe, info);return 0 ;
drivers/irqchip/irq-gic-v4.c +11 -0
@@ -258,6 +258,17 @@ int its_make_vpe_resident(struct its_vpe *vpe, bool g0en, bool g1en)return ret; } +int its_wait_vpt (struct its_vpe *vpe) +{ +struct its_cmd_info info = { }; + +WARN_ON (preemptible ()); + + info.cmd_type =WAIT_VPT ; + +return its_send_vpe_cmd (vpe, &info); +} +int its_invall_vpe (struct its_vpe *vpe) {struct its_cmd_info info = {
include/kvm/arm_vgic.h +3 -0
@@ -402,6 +402,9 @@ int kvm_vgic_v4_unset_forwarding(struct kvm *kvm, int irq, struct kvm_kernel_irq_routing_entry *irq_entry);int vgic_v4_load (struct kvm_vcpu *vcpu); + +void vgic_v4_wait_vpt (struct kvm_vcpu *vcpu); +int vgic_v4_put (struct kvm_vcpu *vcpu,bool need_db);#endif /* __KVM_ARM_VGIC_H */
include/linux/irqchip/arm-gic-v4.h +4 -0
@@ -75,6 +75,8 @@ struct its_vpe {u16 vpe_id;/* Pending VLPIs on schedule out? */ bool pending_last; +/* VPT parse complete */ +bool vpt_ready; };/*
@@ -103,6 +105,7 @@ enum its_vcpu_info_cmd_type {PROP_UPDATE_VLPI ,PROP_UPDATE_AND_INV_VLPI ,SCHEDULE_VPE , +WAIT_VPT ,DESCHEDULE_VPE ,INVALL_VPE , PROP_UPDATE_VSGI,
@@ -128,6 +131,7 @@ struct its_cmd_info {int its_alloc_vcpu_irqs (struct its_vm *vm);void its_free_vcpu_irqs (struct its_vm *vm);int its_make_vpe_resident (struct its_vpe *vpe,bool g0en,bool g1en); +int its_wait_vpt (struct its_vpe *vpe);int its_make_vpe_non_resident (struct its_vpe *vpe,bool db);int its_invall_vpe (struct its_vpe *vpe);int its_map_vlpi (int irq,struct its_vlpi_map *map);
Signature · 1 line
2.19.1
Hi Marc,
Friendly ping, it is some time since I sent this patch according to your last advice...
Besides, recently we found that the mmio delay on GICv4.1 system is about 10 times higher than that on GICv4.0 system in kvm-unit-tests (the specific data is as follows). By the way, HiSilicon GICv4.1 has already been implemented and will be released with our next-generation server, which is almost the only implementation of GICv4.1 at present.
| GICv4.1 emulator | GICv4.0 emulator mmio_read_user (ns) | 12811 | 1598
After analysis, this is mainly caused by the 10 us delay in its_wait_vpt_parse_complete() (the above difference is just about 10 us)...
What's your opinion about this?
Thanks,
Shenming
Quoted 186 lines · Shenming Lu
Right after a vPE is made resident, the code starts polling the GICR_VPENDBASER.Dirty bit until it becomes 0, where the
delay_usis set to 10. But in our measurement, it takes only hundreds of nanoseconds, or 1~2 microseconds, to finish parsing the VPT in most cases. And we also measured the time fromvcpu_load()(include it) to__guest_enter()on Kunpeng 920. On average, it takes 2.55 microseconds (not first run && the VPT is empty). So 10 microseconds delay might really hurt performance.To avoid this, we can set the
delay_usto 1, which is more appropriate in this situation and universal. Besides, we can delay the execution ofits_wait_vpt_parse_complete()(call it fromkvm_vgic_flush_hwstate()corresponding to vPE resident), giving the GIC a chance to work in parallel with the CPU on the entry path.Signed-off-by Shenming Lu <[email protected]>--- arch/arm64/kvm/vgic/vgic-v4.c | 18 ++++++++++++++++++ arch/arm64/kvm/vgic/vgic.c | 2 ++ drivers/irqchip/irq-gic-v3-its.c | 14 +++++++++++--- drivers/irqchip/irq-gic-v4.c | 11 +++++++++++ include/kvm/arm_vgic.h | 3 +++ include/linux/irqchip/arm-gic-v4.h | 4 ++++ 6 files changed, 49 insertions(+), 3 deletions(-)arch/arm64/kvm/vgic/vgic-v4.c +18
-0@@ -353,6 +353,24 @@ int vgic_v4_load(struct kvm_vcpu *vcpu)return err; } +void vgic_v4_wait_vpt (struct kvm_vcpu *vcpu) +{ +struct its_vpe *vpe; + +if (kvm_vgic_global_state.type ==VGIC_V2 || !vgic_supports_direct_msis (vcpu->kvm)) +return ; + + vpe = &vcpu->arch.vgic_cpu.vgic_v3.its_vpe; + +if (vpe->vpt_ready) +return ; + +if (its_wait_vpt (vpe)) +return ; + + vpe->vpt_ready = true; +} +static struct vgic_its *vgic_get_its (struct kvm *kvm,struct kvm_kernel_irq_routing_entry *irq_entry) {arch/arm64/kvm/vgic/vgic.c +2
-0@@ -915,6 +915,8 @@ void kvm_vgic_flush_hwstate(struct kvm_vcpu *vcpu)if (can_access_vgic_from_kernel ())vgic_restore_state (vcpu); + +vgic_v4_wait_vpt (vcpu); }void kvm_vgic_load (struct kvm_vcpu *vcpu)drivers/irqchip/irq-gic-v3-its.c +11
-3@@ -3803,7 +3803,7 @@ static void its_wait_vpt_parse_complete(void)WARN_ON_ONCE (readq_relaxed_poll_timeout_atomic (vlpi_base +GICR_VPENDBASER , val, !(val & GICR_VPENDBASER_Dirty), -10 ,500 )); +1 ,500 )); }static void its_vpe_schedule (struct its_vpe *vpe)@@ -3837,7 +3837,7 @@ static void its_vpe_schedule(struct its_vpe *vpe) val |= GICR_VPENDBASER_Valid;gicr_write_vpendbaser (val, vlpi_base +GICR_VPENDBASER ); -its_wait_vpt_parse_complete (); + vpe->vpt_ready = false; }static void its_vpe_deschedule (struct its_vpe *vpe)@@ -3881,6 +3881,10 @@ static int its_vpe_set_vcpu_affinity(struct irq_data *d, void *vcpu_info)its_vpe_schedule (vpe);return 0 ; +case WAIT_VPT : +its_wait_vpt_parse_complete (); +return 0 ; +case DESCHEDULE_VPE :its_vpe_deschedule (vpe);return 0 ;@@ -4047,7 +4051,7 @@ static void its_vpe_4_1_schedule(struct its_vpe *vpe,gicr_write_vpendbaser (val, vlpi_base +GICR_VPENDBASER ); -its_wait_vpt_parse_complete (); + vpe->vpt_ready = false; } static void its_vpe_4_1_deschedule(struct its_vpe *vpe,@@ -4118,6 +4122,10 @@ static int its_vpe_4_1_set_vcpu_affinity(struct irq_data *d, void *vcpu_info)its_vpe_4_1_schedule (vpe, info);return 0 ; +case WAIT_VPT : +its_wait_vpt_parse_complete (); +return 0 ; +case DESCHEDULE_VPE :its_vpe_4_1_deschedule (vpe, info);return 0 ;drivers/irqchip/irq-gic-v4.c +11
-0@@ -258,6 +258,17 @@ int its_make_vpe_resident(struct its_vpe *vpe, bool g0en, bool g1en)return ret; } +int its_wait_vpt (struct its_vpe *vpe) +{ +struct its_cmd_info info = { }; + +WARN_ON (preemptible ()); + + info.cmd_type =WAIT_VPT ; + +return its_send_vpe_cmd (vpe, &info); +} +int its_invall_vpe (struct its_vpe *vpe) {struct its_cmd_info info = {include/kvm/arm_vgic.h +3
-0@@ -402,6 +402,9 @@ int kvm_vgic_v4_unset_forwarding(struct kvm *kvm, int irq, struct kvm_kernel_irq_routing_entry *irq_entry);int vgic_v4_load (struct kvm_vcpu *vcpu); + +void vgic_v4_wait_vpt (struct kvm_vcpu *vcpu); +int vgic_v4_put (struct kvm_vcpu *vcpu,bool need_db);#endif /* __KVM_ARM_VGIC_H */ include/linux/irqchip/arm-gic-v4.h +4
-0@@ -75,6 +75,8 @@ struct its_vpe {u16 vpe_id;/* Pending VLPIs on schedule out? */ bool pending_last; +/* VPT parse complete */ +bool vpt_ready; };/* @@ -103,6 +105,7 @@ enum its_vcpu_info_cmd_type {PROP_UPDATE_VLPI ,PROP_UPDATE_AND_INV_VLPI ,SCHEDULE_VPE , +WAIT_VPT ,DESCHEDULE_VPE ,INVALL_VPE , PROP_UPDATE_VSGI,@@ -128,6 +131,7 @@ struct its_cmd_info {int its_alloc_vcpu_irqs (struct its_vm *vm);void its_free_vcpu_irqs (struct its_vm *vm);int its_make_vpe_resident (struct its_vpe *vpe,bool g0en,bool g1en); +int its_wait_vpt (struct its_vpe *vpe);int its_make_vpe_non_resident (struct its_vpe *vpe,bool db);int its_invall_vpe (struct its_vpe *vpe);int its_map_vlpi (int irq,struct its_vlpi_map *map);
Marc Zyngier
maintainerShenming,
Somehow this patch ended up in the wrong folder.
Apologies for the delay reviewing it.
Quoted 30 lines · Shenming Lu
Right after a vPE is made resident, the code starts polling the GICR_VPENDBASER.Dirty bit until it becomes 0, where the
delay_usis set to 10. But in our measurement, it takes only hundreds of nanoseconds, or 1~2 microseconds, to finish parsing the VPT in most cases. And we also measured the time fromvcpu_load()(include it) to__guest_enter()on Kunpeng 920. On average, it takes 2.55 microseconds (not first run && the VPT is empty). So 10 microseconds delay might really hurt performance.To avoid this, we can set the
delay_usto 1, which is more appropriate in this situation and universal. Besides, we can delay the execution ofits_wait_vpt_parse_complete()(call it fromkvm_vgic_flush_hwstate()corresponding to vPE resident), giving the GIC a chance to work in parallel with the CPU on the entry path.Signed-off-by Shenming Lu <[email protected]>--- arch/arm64/kvm/vgic/vgic-v4.c | 18 ++++++++++++++++++ arch/arm64/kvm/vgic/vgic.c | 2 ++ drivers/irqchip/irq-gic-v3-its.c | 14 +++++++++++--- drivers/irqchip/irq-gic-v4.c | 11 +++++++++++ include/kvm/arm_vgic.h | 3 +++ include/linux/irqchip/arm-gic-v4.h | 4 ++++ 6 files changed, 49 insertions(+), 3 deletions(-)arch/arm64/kvm/vgic/vgic-v4.c +0
-0
arch/arm64/kvm/vgic/vgic-v4.c int vgic_v4_load(struct kvm_vcpu *vcpu) · line 356
Quoted 4 lines
arch/arm64/kvm/vgic/vgic-v4.c +1
-0@@ -353,6 +353,24 @@ int vgic_v4_load(struct kvm_vcpu *vcpu)return err; } +void vgic_v4_wait_vpt (struct kvm_vcpu *vcpu)
I'd like something a bit more abstract as a name.
vgic_v4_commit() seems more appropriate, and could be used for other purposes.
arch/arm64/kvm/vgic/vgic-v4.c int vgic_v4_load(struct kvm_vcpu *vcpu)
Quoted 4 lines
arch/arm64/kvm/vgic/vgic-v4.c +4
-0+{ +struct its_vpe *vpe; + + if (kvm_vgic_global_state.type == VGIC_V2 ||
Why do you test for GICv2? Isn't the vgic_supports_direct_msis() test enough? And the test should be moved to kvm_vgic_flush_hwstate(), as we already have similar checks there.
arch/arm64/kvm/vgic/vgic-v4.c int vgic_v4_load(struct kvm_vcpu *vcpu) · line 369
Quoted 10 lines
arch/arm64/kvm/vgic/vgic-v4.c +9
-0!vgic_supports_direct_msis(vcpu->kvm)) +return ; + + vpe = &vcpu->arch.vgic_cpu.vgic_v3.its_vpe; + +if (vpe->vpt_ready) +return ; + +if (its_wait_vpt (vpe)) +return ;
How can that happen?
arch/arm64/kvm/vgic/vgic-v4.c int vgic_v4_load(struct kvm_vcpu *vcpu) · line 372
Quoted 2 lines
arch/arm64/kvm/vgic/vgic-v4.c +2
-0+ + vpe->vpt_ready = true;
This is nasty. You need to explain what happens with this state (you are trying not to access VPENDBASER across a shallow exit, as only a vcpu_put will invalidate the GIC state). And something like vpe_ready is more generic (we try not to have too much of the GICv4 gunk in the KVM code).
Quoted 23 lines
arch/arm64/kvm/vgic/vgic-v4.c +2
-0+} +static struct vgic_its *vgic_get_its (struct kvm *kvm,struct kvm_kernel_irq_routing_entry *irq_entry){
arch/arm64/kvm/vgic/vgic.c +2
-0@@ -915,6 +915,8 @@ void kvm_vgic_flush_hwstate(struct kvm_vcpu *vcpu)if (can_access_vgic_from_kernel ())vgic_restore_state (vcpu); + +vgic_v4_wait_vpt (vcpu); }void kvm_vgic_load (struct kvm_vcpu *vcpu)drivers/irqchip/irq-gic-v3-its.c +0
-0
drivers/irqchip/irq-gic-v3-its.c static void its_wait_vpt_parse_complete(void) · line 3807
Quoted 6 lines
drivers/irqchip/irq-gic-v3-its.c +1
-1@@ -3803,7 +3803,7 @@ static void its_wait_vpt_parse_complete(void)WARN_ON_ONCE (readq_relaxed_poll_timeout_atomic (vlpi_base +GICR_VPENDBASER , val, !(val & GICR_VPENDBASER_Dirty), -10 ,500 )); +1 ,500 ));
This really should be in a separate patch.
drivers/irqchip/irq-gic-v3-its.c static void its_vpe_schedule(struct its_vpe *vpe) · line 3840
Quoted 9 lines
drivers/irqchip/irq-gic-v3-its.c +0
-0}static void
its_vpe_schedule(struct its_vpe *vpe)drivers/irqchip/irq-gic-v3-its.c +1
-1@@ -3837,7 +3837,7 @@ static void its_vpe_schedule(struct its_vpe *vpe) val |= GICR_VPENDBASER_Valid;gicr_write_vpendbaser (val, vlpi_base +GICR_VPENDBASER ); -its_wait_vpt_parse_complete (); + vpe->vpt_ready = false;
This really belongs to the deschedule path, doesn't it? Given that it can only be set from vgic_flush_hwstate(), it should be fairly foolproof.
drivers/irqchip/irq-gic-v3-its.c static int its_vpe_set_vcpu_affinity(struct · line 3885
Quoted 9 lines
drivers/irqchip/irq-gic-v3-its.c +1
-0}static void its_vpe_deschedule (struct its_vpe *vpe)@@ -3881,6 +3881,10 @@ static int its_vpe_set_vcpu_affinity(struct irq_data *d, void *vcpu_info)its_vpe_schedule (vpe);return 0 ; +case WAIT_VPT :
COMMIT_VPE seems a better name.
Quoted 33 lines
drivers/irqchip/irq-gic-v3-its.c +3
-0+its_wait_vpt_parse_complete (); +return 0 ; +case DESCHEDULE_VPE :its_vpe_deschedule (vpe);drivers/irqchip/irq-gic-v3-its.c +1
-1return 0 ;@@ -4047,7 +4051,7 @@ static void its_vpe_4_1_schedule(struct its_vpe *vpe,gicr_write_vpendbaser (val, vlpi_base +GICR_VPENDBASER ); -its_wait_vpt_parse_complete (); + vpe->vpt_ready = false; }static void its_vpe_4_1_deschedule(struct
its_vpe*vpe,drivers/irqchip/irq-gic-v3-its.c +4
-0@@ -4118,6 +4122,10 @@ static int its_vpe_4_1_set_vcpu_affinity(struct irq_data *d, void *vcpu_info)its_vpe_4_1_schedule (vpe, info);return 0 ; +case WAIT_VPT : +its_wait_vpt_parse_complete (); +return 0 ; +case DESCHEDULE_VPE :its_vpe_4_1_deschedule (vpe, info);drivers/irqchip/irq-gic-v3-its.c +0
-0return 0 ;drivers/irqchip/irq-gic-v4.c +0
-0
drivers/irqchip/irq-gic-v4.c int its_make_vpe_resident(struct its_vpe *vpe, · line 262
Quoted 5 lines
drivers/irqchip/irq-gic-v4.c +1
-0@@ -258,6 +258,17 @@ int its_make_vpe_resident(struct its_vpe *vpe, bool g0en, bool g1en) return ret; } +int its_wait_vpt (struct its_vpe *vpe)
its_commit_vpe()
drivers/irqchip/irq-gic-v4.c int its_make_vpe_resident(struct its_vpe *vpe, bool g0en, bool g1en) · line 267
Quoted 6 lines
drivers/irqchip/irq-gic-v4.c +6
-0+{ +struct its_cmd_info info = { }; + +WARN_ON (preemptible ()); + + info.cmd_type =WAIT_VPT ;
Please write it as:
struct its_cmd_info = {
.cmd_type = COMMIT_VPE,
};as for most of the commands.
Quoted 45 lines
drivers/irqchip/irq-gic-v4.c +4
-0+ +return its_send_vpe_cmd (vpe, &info); +} +int its_invall_vpe (struct its_vpe *vpe) {drivers/irqchip/irq-gic-v4.c +0
-0struct its_cmd_info info = {include/kvm/arm_vgic.h +3
-0@@ -402,6 +402,9 @@ int kvm_vgic_v4_unset_forwarding(struct kvm *kvm,int irq, struct kvm_kernel_irq_routing_entry *irq_entry);int vgic_v4_load (struct kvm_vcpu *vcpu); + +void vgic_v4_wait_vpt (struct kvm_vcpu *vcpu); +int vgic_v4_put (struct kvm_vcpu *vcpu,bool need_db);#endif /*
__KVM_ARM_VGIC_H*/include/linux/irqchip/arm-gic-v4.h +3
-0@@ -75,6 +75,8 @@ struct its_vpe {u16 vpe_id;/* Pending VLPIs on schedule out? */ bool pending_last; +/* VPT parse complete */ +bool vpt_ready; };/* @@ -103,6 +105,7 @@ enum its_vcpu_info_cmd_type {PROP_UPDATE_VLPI ,PROP_UPDATE_AND_INV_VLPI ,SCHEDULE_VPE , +WAIT_VPT ,DESCHEDULE_VPE ,INVALL_VPE , PROP_UPDATE_VSGI,
include/linux/irqchip/arm-gic-v4.h struct its_cmd_info { · line 137
Quoted 7 lines
include/linux/irqchip/arm-gic-v4.h +1
-0@@ -128,6 +131,7 @@ struct its_cmd_info {int its_alloc_vcpu_irqs (struct its_vm *vm);void its_free_vcpu_irqs (struct its_vm *vm);int its_make_vpe_resident (struct its_vpe *vpe,bool g0en,bool g1en); +int its_wait_vpt (struct its_vpe *vpe);int its_make_vpe_non_resident (struct its_vpe *vpe,bool db);int its_invall_vpe (struct its_vpe *vpe);int its_map_vlpi (int irq,struct its_vlpi_map *map);
My comments are mostly cosmetic. If you can respin quickly, I'll pick it up for 5.11.
Thanks,
M.
Signature · 5 lines
Jazz is not dead. It just smells funny... _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
Quoted 38 lines · Marc Zyngier
Shenming,
Somehow this patch ended up in the wrong folder.
Apologies for the delay reviewing it.>Quoted 33 lines · Shenming Lu
Right after a vPE is made resident, the code starts polling the GICR_VPENDBASER.Dirty bit until it becomes 0, where the
delay_usis set to 10. But in our measurement, it takes only hundreds of nanoseconds, or 1~2 microseconds, to finish parsing the VPT in most cases. And we also measured the time fromvcpu_load()(include it) to__guest_enter()on Kunpeng 920. On average, it takes 2.55 microseconds (not first run && the VPT is empty). So 10 microseconds delay might really hurt performance.To avoid this, we can set the
delay_usto 1, which is more appropriate in this situation and universal. Besides, we can delay the execution ofits_wait_vpt_parse_complete()(call it fromkvm_vgic_flush_hwstate()corresponding to vPE resident), giving the GIC a chance to work in parallel with the CPU on the entry path.Signed-off-by Shenming Lu <[email protected]>---
arch/arm64/kvm/vgic/vgic-v4.c | 18 ++++++++++++++++++ arch/arm64/kvm/vgic/vgic.c | 2 ++ drivers/irqchip/irq-gic-v3-its.c | 14 +++++++++++--- drivers/irqchip/irq-gic-v4.c | 11 +++++++++++ include/kvm/arm_vgic.h | 3 +++include/linux/irqchip/arm-gic-v4.h| 4 ++++6 files changed, 49 insertions(+), 3 deletions(-)arch/arm64/kvm/vgic/vgic-v4.c +0
-0@@ -353,6 +353,24 @@ int vgic_v4_load(struct kvm_vcpu *vcpu) return err; }
Quoted 6 lines
arch/arm64/kvm/vgic/vgic-v4.c int vgic_v4_load(struct kvm_vcpu *vcpu) · line 356
Quoted 1 line
arch/arm64/kvm/vgic/vgic-v4.c +1
-0+void vgic_v4_wait_vpt (struct kvm_vcpu *vcpu)I'd like something a bit more abstract as a name.
vgic_v4_commit()seems more appropriate, and could be used for other purposes.
Yes, it looks more appropriate.
Quoted 9 lines
arch/arm64/kvm/vgic/vgic-v4.c int vgic_v4_load(struct kvm_vcpu *vcpu)
Quoted 5 lines
arch/arm64/kvm/vgic/vgic-v4.c +4
-0+{ + struct its_vpe *vpe; + + if (kvm_vgic_global_state.type == VGIC_V2 ||Why do you test for GICv2? Isn't the
vgic_supports_direct_msis()test enough? And the test should be moved tokvm_vgic_flush_hwstate(), as we already have similar checks there.
Yes, the test for GICv2 is unnecessary.... I will correct it.
Quoted 13 lines
arch/arm64/kvm/vgic/vgic-v4.c int vgic_v4_load(struct kvm_vcpu *vcpu) · line 369
Quoted 11 lines
arch/arm64/kvm/vgic/vgic-v4.c +9
-0!vgic_supports_direct_msis(vcpu->kvm)) + return; + + vpe = &vcpu->arch.vgic_cpu.vgic_v3.its_vpe; + + if (vpe->vpt_ready) + return; + + if (its_wait_vpt(vpe)) + return;How can that happen?
Yes, it seems that its_wait_vpt() would always return 0.
Quoted 6 lines
arch/arm64/kvm/vgic/vgic-v4.c int vgic_v4_load(struct kvm_vcpu *vcpu) · line 372
Quoted 3 lines
arch/arm64/kvm/vgic/vgic-v4.c +2
-0+ + vpe->vpt_ready = true;This is nasty. You need to explain what happens with this state (you are trying not to access VPENDBASER across a shallow exit, as only a
vcpu_put
Ok, I will add a comment here.
Quoted 2 lines
will invalidate the GIC state). And something like
vpe_readyis more generic (we try not to have too much of the GICv4 gunk in the KVM code).
Yes, that's better.
Quoted 18 lines
Quoted 18 lines
arch/arm64/kvm/vgic/vgic-v4.c +2
-0+} + static struct vgic_its *vgic_get_its(struct kvm *kvm, struct kvm_kernel_irq_routing_entry *irq_entry){
arch/arm64/kvm/vgic/vgic.c +2
-0@@ -915,6 +915,8 @@ void kvm_vgic_flush_hwstate(struct kvm_vcpu *vcpu) if (can_access_vgic_from_kernel()) vgic_restore_state(vcpu); + + vgic_v4_wait_vpt(vcpu); }
Quoted 13 lines
drivers/irqchip/irq-gic-v3-its.c static void its_wait_vpt_parse_complete(void) · line 3806
Quoted 11 lines
arch/arm64/kvm/vgic/vgic.c +0
-0void kvm_vgic_load(struct kvm_vcpu *vcpu)drivers/irqchip/irq-gic-v3-its.c +1
-1@@ -3803,7 +3803,7 @@ static void its_wait_vpt_parse_complete(void) WARN_ON_ONCE(readq_relaxed_poll_timeout_atomic(vlpi_base + GICR_VPENDBASER, val, !(val & GICR_VPENDBASER_Dirty), - 10, 500)); + 1, 500));This really should be in a separate patch.
Ok, I will separate it.
Quoted 8 lines
Quoted 8 lines
drivers/irqchip/irq-gic-v3-its.c +0
-0} static void its_vpe_schedule(struct its_vpe *vpe)@@ -3837,7 +3837,7 @@ static void its_vpe_schedule(struct its_vpe *vpe) val |= GICR_VPENDBASER_Valid; gicr_write_vpendbaser(val, vlpi_base + GICR_VPENDBASER);
Quoted 6 lines
drivers/irqchip/irq-gic-v3-its.c static void its_vpe_schedule(struct its_vpe *vpe) · line 3840
Quoted 2 lines
drivers/irqchip/irq-gic-v3-its.c +1
-1- its_wait_vpt_parse_complete(); + vpe->vpt_ready = false;This really belongs to the deschedule path, doesn't it? Given that it can only be set from
vgic_flush_hwstate(), it should be fairly foolproof.
Yes, that's better.
Quoted 9 lines
Quoted 9 lines
drivers/irqchip/irq-gic-v3-its.c +0
-0} static void its_vpe_deschedule(struct its_vpe *vpe)@@ -3881,6 +3881,10 @@ static int its_vpe_set_vcpu_affinity(struct irq_data *d, void *vcpu_info) its_vpe_schedule(vpe); return 0;
Quoted 3 lines
drivers/irqchip/irq-gic-v3-its.c static int its_vpe_set_vcpu_affinity(struct · line 3885
Quoted 1 line
drivers/irqchip/irq-gic-v3-its.c +1
-0+ case WAIT_VPT:
COMMIT_VPEseems a better name.
Yes, that's better.
Quoted 50 lines
Quoted 33 lines
drivers/irqchip/irq-gic-v3-its.c +3
-0+ its_wait_vpt_parse_complete(); + return 0; +case
DESCHEDULE_VPE:
its_vpe_deschedule(vpe);
return 0;drivers/irqchip/irq-gic-v3-its.c +5
-1@@ -4047,7 +4051,7 @@ static void its_vpe_4_1_schedule(struct its_vpe *vpe, gicr_write_vpendbaser(val, vlpi_base + GICR_VPENDBASER); - its_wait_vpt_parse_complete(); + vpe->vpt_ready = false; } static void its_vpe_4_1_deschedule(struct its_vpe *vpe,@@ -4118,6 +4122,10 @@ static int its_vpe_4_1_set_vcpu_affinity(struct irq_data *d, void *vcpu_info) its_vpe_4_1_schedule(vpe, info); return 0; + case WAIT_VPT: + its_wait_vpt_parse_complete(); + return 0; +case
DESCHEDULE_VPE:
its_vpe_4_1_deschedule(vpe, info);
return 0;drivers/irqchip/irq-gic-v4.c +0
-0drivers/irqchip/irq-gic-v4.c int its_make_vpe_resident(struct its_vpe *vpe, · line 262
Quoted 5 lines
drivers/irqchip/irq-gic-v4.c +1
-0@@ -258,6 +258,17 @@ int its_make_vpe_resident(struct its_vpe *vpe, bool g0en, bool g1en) return ret; } +int its_wait_vpt (struct its_vpe *vpe)
its_commit_vpe()drivers/irqchip/irq-gic-v4.c int its_make_vpe_resident(struct its_vpe *vpe, bool g0en, bool g1en) · line 267
Quoted 6 lines
drivers/irqchip/irq-gic-v4.c +6
-0+{ + struct its_cmd_info info = { }; + + WARN_ON(preemptible()); + + info.cmd_type = WAIT_VPT;Please write it as:
Quoted 5 lines
struct
its_cmd_info= {
.cmd_type =COMMIT_VPE,
};as for most of the commands.
Ok, I will correct it.
Quoted 47 lines
Quoted 47 lines
drivers/irqchip/irq-gic-v4.c +4
-0+ + return its_send_vpe_cmd(vpe, &info); +} + int its_invall_vpe(struct its_vpe *vpe) {struct
its_cmd_infoinfo = {include/kvm/arm_vgic.h +3
-0@@ -402,6 +402,9 @@ int kvm_vgic_v4_unset_forwarding(struct kvm *kvm, int irq, struct kvm_kernel_irq_routing_entry *irq_entry); int vgic_v4_load(struct kvm_vcpu *vcpu); + +void vgic_v4_wait_vpt (struct kvm_vcpu *vcpu); + int vgic_v4_put(struct kvm_vcpu *vcpu, bool need_db); #endif /* __KVM_ARM_VGIC_H */include/linux/irqchip/arm-gic-v4.h +3
-0@@ -75,6 +75,8 @@ struct its_vpe { u16 vpe_id; /* Pending VLPIs on schedule out? */ bool pending_last; + /* VPT parse complete */ + bool vpt_ready; }; /*@@ -103,6 +105,7 @@ enum its_vcpu_info_cmd_type { PROP_UPDATE_VLPI, PROP_UPDATE_AND_INV_VLPI, SCHEDULE_VPE, + WAIT_VPT, DESCHEDULE_VPE, INVALL_VPE, PROP_UPDATE_VSGI,@@ -128,6 +131,7 @@ struct its_cmd_info { int its_alloc_vcpu_irqs(struct its_vm *vm); void its_free_vcpu_irqs(struct its_vm *vm);
Quoted 8 lines
include/linux/irqchip/arm-gic-v4.h struct its_cmd_info { · line 137
Quoted 5 lines
include/linux/irqchip/arm-gic-v4.h +1
-0int its_make_vpe_resident(struct its_vpe *vpe, bool g0en, bool g1en); +int its_wait_vpt (struct its_vpe *vpe); int its_make_vpe_non_resident(struct its_vpe *vpe, bool db); int its_invall_vpe(struct its_vpe *vpe); int its_map_vlpi(int irq, struct its_vlpi_map *map);My comments are mostly cosmetic. If you can respin quickly, I'll pick it up for 5.11.
Ok, I will try to respin it quickly.
Thanks for reviewing, :)
Shenming
Quoted 4 lines
Thanks,
M.
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel