diff options
author | Christoffer Dall <christoffer.dall@arm.com> | 2019-01-10 15:33:52 +0100 |
---|---|---|
committer | Marc Zyngier <marc.zyngier@arm.com> | 2019-02-07 11:44:47 +0000 |
commit | ab2d5eb03dbb7b37a1c6356686fb48626ab0c93e (patch) | |
tree | da83d4d0e109e1a50589bba27dda08564b6b35e0 /fs/bfs | |
parent | 20589c8cc47dce5854c8bf1b44a9fc63d798d26d (diff) | |
download | linux-ab2d5eb03dbb7b37a1c6356686fb48626ab0c93e.tar.gz linux-ab2d5eb03dbb7b37a1c6356686fb48626ab0c93e.tar.bz2 linux-ab2d5eb03dbb7b37a1c6356686fb48626ab0c93e.zip |
KVM: arm/arm64: vgic: Always initialize the group of private IRQs
We currently initialize the group of private IRQs during
kvm_vgic_vcpu_init, and the value of the group depends on the GIC model
we are emulating. However, CPUs created before creating (and
initializing) the VGIC might end up with the wrong group if the VGIC
is created as GICv3 later.
Since we have no enforced ordering of creating the VGIC and creating
VCPUs, we can end up with part the VCPUs being properly intialized and
the remaining incorrectly initialized. That also means that we have no
single place to do the per-cpu data structure initialization which
depends on knowing the emulated GIC model (which is only the group
field).
This patch removes the incorrect comment from kvm_vgic_vcpu_init and
initializes the group of all previously created VCPUs's private
interrupts in vgic_init in addition to the existing initialization in
kvm_vgic_vcpu_init.
Signed-off-by: Christoffer Dall <christoffer.dall@arm.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'fs/bfs')
0 files changed, 0 insertions, 0 deletions