mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: tip-bot for NeilBrown <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: rjw@rjwysocki.net, peterz@infradead.org, mingo@kernel.org,
	neil@brown.name, linux-kernel@vger.kernel.org,
	kalle.jokiniemi@jollamobile.com, tglx@linutronix.de,
	gta04-owner@goldelico.com, hpa@zytor.com, neilb@suse.de
Subject: [tip:irq/core] genirq: Don' t suspend nested_thread irqs over system suspend
Date: Mon, 18 May 2015 08:27:31 -0700	[thread overview]
Message-ID: <tip-3c646f2c6aa9e918d7fc77867df7f430059f9ccc@git.kernel.org> (raw)
In-Reply-To: <20150517151934.2393e8f8@notabene.brown>

Commit-ID:  3c646f2c6aa9e918d7fc77867df7f430059f9ccc
Gitweb:     http://git.kernel.org/tip/3c646f2c6aa9e918d7fc77867df7f430059f9ccc
Author:     NeilBrown <neilb@suse.de>
AuthorDate: Sun, 17 May 2015 15:19:34 +1000
Committer:  Thomas Gleixner <tglx@linutronix.de>
CommitDate: Mon, 18 May 2015 17:23:47 +0200

genirq: Don't suspend nested_thread irqs over system suspend

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 <neil@brown.name>
Cc: GTA04 owners <gta04-owner@goldelico.com>
Cc: Kalle Jokiniemi <kalle.jokiniemi@jollamobile.com>
Acked-by: Peter Zijlstra <peterz@infradead.org>
Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
Link: http://lkml.kernel.org/r/20150517151934.2393e8f8@notabene.brown
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

---
 kernel/irq/pm.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/kernel/irq/pm.c b/kernel/irq/pm.c
index 5204a6d..d22786a 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)
 			continue;
+		if (irq_settings_is_nested_thread(desc))
+			continue;
 
 		raw_spin_lock_irqsave(&desc->lock, flags);
 		resume_irq(desc, irq);

      parent reply	other threads:[~2015-05-18 15:28 UTC|newest]

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

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=tip-3c646f2c6aa9e918d7fc77867df7f430059f9ccc@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=gta04-owner@goldelico.com \
    --cc=hpa@zytor.com \
    --cc=kalle.jokiniemi@jollamobile.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=neil@brown.name \
    --cc=neilb@suse.de \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome