• Suresh Siddha's avatar
    x86: Remove move_cleanup_count from irq_cfg · 23359a88
    Suresh Siddha authored
    move_cleanup_count for each irq in irq_cfg is keeping track of
    the total number of cpus that need to free the corresponding
    vectors associated with the irq which has now been migrated to
    new destination. As long as this move_cleanup_count is non-zero
    (i.e., as long as we have n't freed the vector allocations on
    the old destinations) we were preventing the irq's further
    migration.
    
    This cleanup count is unnecessary and it is enough to not allow
    the irq migration till we send the cleanup vector to the
    previous irq destination, for which we already have irq_cfg's
    move_in_progress.  All we need to make sure is that we free the
    vector at the old desintation but we don't need to wait till
    that gets freed.
    Signed-off-by: default avatarSuresh Siddha <suresh.b.siddha@intel.com>
    Acked-by: default avatarGary Hade <garyhade@us.ibm.com>
    Cc: Eric W. Biederman <ebiederm@xmission.com>
    LKML-Reference: <20091026230001.752968906@sbs-t61.sc.intel.com>
    Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
    23359a88
io_apic.c 98.4 KB