[lkml]   [2010]   [Jul]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[PATCH 4/4] xen: do not suspend IPI IRQs.
    In general the semantics of IPIs are that they are are expected to
    continue functioning after dpm_suspend_noirq().

    Specifically I have seen a deadlock between the callfunc IPI and the
    stop machine used by xen's do_suspend() routine. If one CPU has already
    called dpm_suspend_noirq() then there is a window where it can be sent
    a callfunc IPI before all the other CPUs have entered stop_cpu().

    If this happens then the first CPU ends up spinning in stop_cpu()
    waiting for the other to rendezvous in state STOPMACHINE_PREPARE while
    the other is spinning in csd_lock_wait().

    Signed-off-by: Ian Campbell <>
    Cc: Thomas Gleixner <>
    Cc: Jeremy Fitzhardinge <>
    Cc: <> # .32.x+: 517d6934: irq: rename IRQF_TIMER to IRQF_NO_SUSPEND
    Cc: <> # .32.x+
    drivers/xen/events.c | 1 +
    1 files changed, 1 insertions(+), 0 deletions(-)

    diff --git a/drivers/xen/events.c b/drivers/xen/events.c
    index db8f506..28f133a 100644
    --- a/drivers/xen/events.c
    +++ b/drivers/xen/events.c
    @@ -536,6 +536,7 @@ int bind_ipi_to_irqhandler(enum ipi_vector ipi,
    if (irq < 0)
    return irq;

    + irqflags |= IRQF_NO_SUSPEND;
    retval = request_irq(irq, handler, irqflags, devname, dev_id);
    if (retval != 0) {

     \ /
      Last update: 2010-07-28 12:57    [W:0.021 / U:17.696 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site