redonkable
/
remarkable-linux
1
0
Fork 0
Code Releases Activity

KVM: arm/arm64: vgic: Don't check vgic_initialized in sync/flush 

Now when we do an early init of the static parts of the VGIC data
structures, we can do things like checking if the AP lists are empty
directly without having to explicitly check if the vgic is initialized
and reduce a bit of work in our critical path.

Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Christoffer Dall <cdall@linaro.org>
zero-colors
Christoffer Dall 2017-03-18 13:41:54 +01:00
parent 966e014919
commit 0b09b6e519
1 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
virt/kvm/arm/vgic/vgic.c
View File

@ -633,9 +633,6 @@ void kvm_vgic_sync_hwstate(struct kvm_vcpu *vcpu)
{
struct vgic_cpu *vgic_cpu = &vcpu->arch.vgic_cpu;
if (unlikely(!vgic_initialized(vcpu->kvm)))
return;
vgic_fold_lr_state(vcpu);
vgic_prune_ap_list(vcpu);
@ -646,9 +643,6 @@ void kvm_vgic_sync_hwstate(struct kvm_vcpu *vcpu)
/* Flush our emulation state into the GIC hardware before entering the guest. */
void kvm_vgic_flush_hwstate(struct kvm_vcpu *vcpu)
{
if (unlikely(!vgic_initialized(vcpu->kvm)))
return;
/*
* If there are no virtual interrupts active or pending for this
* VCPU, then there is no work to do and we can bail out without