Re: [PATCH] KVM: arm/arm64: VGIC: extend !vgic_is_initialized guard

2017-11-20 Thread Christoffer Dall
Hi Andre, On Fri, Nov 17, 2017 at 05:58:21PM +, Andre Przywara wrote: > Commit f39d16cbabf9 ("KVM: arm/arm64: Guard kvm_vgic_map_is_active against > !vgic_initialized") introduced a check whether the VGIC has been > initialized before accessing the spinlock and the VGIC data structure. >

Re: [PATCH] KVM: arm/arm64: VGIC: extend !vgic_is_initialized guard

2017-11-20 Thread Auger Eric
Hi Andre, On 17/11/2017 18:58, Andre Przywara wrote: > Commit f39d16cbabf9 ("KVM: arm/arm64: Guard kvm_vgic_map_is_active against > !vgic_initialized") introduced a check whether the VGIC has been > initialized before accessing the spinlock and the VGIC data structure. > However the

Re: [PATCH] KVM: arm/arm64: VGIC: extend !vgic_is_initialized guard

2017-11-20 Thread Auger Eric
Hi Andre, On 17/11/2017 18:58, Andre Przywara wrote: > Commit f39d16cbabf9 ("KVM: arm/arm64: Guard kvm_vgic_map_is_active against > !vgic_initialized") introduced a check whether the VGIC has been > initialized before accessing the spinlock and the VGIC data structure. > However the

[PATCH] KVM: arm/arm64: VGIC: extend !vgic_is_initialized guard

2017-11-17 Thread Andre Przywara
Commit f39d16cbabf9 ("KVM: arm/arm64: Guard kvm_vgic_map_is_active against !vgic_initialized") introduced a check whether the VGIC has been initialized before accessing the spinlock and the VGIC data structure. However the vgic_get_irq() call in the variable declaration sneaked through the net, so