All of
 help / color / mirror / Atom feed
From: NeilBrown <>
To: Thomas Gleixner <>,
	Peter Zijlstra <>,
	"Rafael J. Wysocki" <>
	GTA04 owners <>,,
	Kalle Jokiniemi <>
Subject: [PATCH - RE-RESEND] IRQ: don't suspend nested_thread irqs over system suspend.
Date: Sun, 17 May 2015 15:19:34 +1000	[thread overview]
Message-ID: <20150517151934.2393e8f8@notabene.brown> (raw)

[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]

Nested IRQs can only fire when the parent irq fires.
So when the parent is suspended, there is no need to suspend
the child irq.

Suspending nested irqs can cause a problem is they are suspended or
resumed in the wrong order.
If an interrupt fires while the parent is active but the child is
suspended, then the interrupt will not be acknowledged properly
and so an interrupt storm can result.
This is particularly likely if the parent is resumed before
the child, and the interrupt was raised during suspend.

Ensuring correct ordering would be possible, but it is simpler
to just never suspend nested interrupts.

Signed-off-by: NeilBrown <>

At Rafael's request I'm resending this.  No response last time (except from Rafael),
no change in the code.

This change will fix a bug so that the work-around introduced by 
  8b41669ceba0 ("mfd: twl4030: Fix chained irq handling on resume from suspend")
can be reverted.  This work-around misuses the IRQF_EARLY_RESUME flag, and triggers
a warning on resume:

[   56.095825] WARNING: CPU: 0 PID: 3 at ../kernel/irq/manage.c:661 irq_nested_primary_handler+0x18/0x28()

(though the line number might have changed).


diff --git a/kernel/irq/pm.c b/kernel/irq/pm.c
index 5204a6d1b985..d22786a6dbde 100644
--- a/kernel/irq/pm.c
+++ b/kernel/irq/pm.c
@@ -123,6 +123,8 @@ void suspend_device_irqs(void)
 		unsigned long flags;
 		bool sync;
+		if (irq_settings_is_nested_thread(desc))
+			continue;
 		raw_spin_lock_irqsave(&desc->lock, flags);
 		sync = suspend_device_irq(desc, irq);
 		raw_spin_unlock_irqrestore(&desc->lock, flags);
@@ -163,6 +165,8 @@ static void resume_irqs(bool want_early)
 		if (!is_early && want_early)
+		if (irq_settings_is_nested_thread(desc))
+			continue;
 		raw_spin_lock_irqsave(&desc->lock, flags);
 		resume_irq(desc, irq);

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

             reply	other threads:[~2015-05-17  5:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-17  5:19 NeilBrown [this message]
2015-05-18 12:16 ` [PATCH - RE-RESEND] IRQ: don't suspend nested_thread irqs over system suspend Peter Zijlstra
2015-05-18 15:27 ` [tip:irq/core] genirq: Don' t " tip-bot for NeilBrown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150517151934.2393e8f8@notabene.brown \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.