lkml.org 
[lkml]   [2019]   [Mar]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH AUTOSEL 4.20 21/52] KVM: arm/arm64: vgic: Always initialize the group of private IRQs
    Date
    From: Christoffer Dall <christoffer.dall@arm.com>

    [ Upstream commit ab2d5eb03dbb7b37a1c6356686fb48626ab0c93e ]

    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>
    Signed-off-by: Sasha Levin <sashal@kernel.org>
    ---
    virt/kvm/arm/vgic/vgic-init.c | 22 ++++++++++++++--------
    1 file changed, 14 insertions(+), 8 deletions(-)

    diff --git a/virt/kvm/arm/vgic/vgic-init.c b/virt/kvm/arm/vgic/vgic-init.c
    index 33e7ee814f7b..8196e4f8731f 100644
    --- a/virt/kvm/arm/vgic/vgic-init.c
    +++ b/virt/kvm/arm/vgic/vgic-init.c
    @@ -231,13 +231,6 @@ int kvm_vgic_vcpu_init(struct kvm_vcpu *vcpu)
    irq->config = VGIC_CONFIG_LEVEL;
    }

    - /*
    - * GICv3 can only be created via the KVM_DEVICE_CREATE API and
    - * so we always know the emulation type at this point as it's
    - * either explicitly configured as GICv3, or explicitly
    - * configured as GICv2, or not configured yet which also
    - * implies GICv2.
    - */
    if (dist->vgic_model == KVM_DEV_TYPE_ARM_VGIC_V3)
    irq->group = 1;
    else
    @@ -281,7 +274,7 @@ int vgic_init(struct kvm *kvm)
    {
    struct vgic_dist *dist = &kvm->arch.vgic;
    struct kvm_vcpu *vcpu;
    - int ret = 0, i;
    + int ret = 0, i, idx;

    if (vgic_initialized(kvm))
    return 0;
    @@ -298,6 +291,19 @@ int vgic_init(struct kvm *kvm)
    if (ret)
    goto out;

    + /* Initialize groups on CPUs created before the VGIC type was known */
    + kvm_for_each_vcpu(idx, vcpu, kvm) {
    + struct vgic_cpu *vgic_cpu = &vcpu->arch.vgic_cpu;
    +
    + for (i = 0; i < VGIC_NR_PRIVATE_IRQS; i++) {
    + struct vgic_irq *irq = &vgic_cpu->private_irqs[i];
    + if (dist->vgic_model == KVM_DEV_TYPE_ARM_VGIC_V3)
    + irq->group = 1;
    + else
    + irq->group = 0;
    + }
    + }
    +
    if (vgic_has_its(kvm)) {
    ret = vgic_v4_init(kvm);
    if (ret)
    --
    2.19.1
    \
     
     \ /
      Last update: 2019-03-11 20:56    [W:3.203 / U:1.400 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site