From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: NeilBrown <neilb@suse.de>, Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
GTA04 owners <gta04-owner@goldelico.com>,
linux-pm@vger.kernel.org,
Kalle Jokiniemi <kalle.jokiniemi@jollamobile.com>
Subject: Re: [PATCH] IRQ: don't suspend nested_thread irqs over system suspend.
Date: Sat, 31 Jan 2015 00:06:37 +0100 [thread overview]
Message-ID: <1465455.9L1ju05BhM@vostro.rjw.lan> (raw)
In-Reply-To: <20150131092545.33ed35b8@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]
On Saturday, January 31, 2015 09:25:45 AM NeilBrown wrote:
>
> 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. This patch does that.
Clever. :-)
This is fine by me. Thomas, what do you think?
> This patch allows the IRQF_EARLY_RESUME to be removed from
> twl4030_sih_setup(). That flag attempts to fix the same problem
> is a very different way, but causes
>
> [ 56.095825] WARNING: CPU: 0 PID: 3 at ../kernel/irq/manage.c:661 irq_nested_primary_handler+0x18/0x28()
> [ 56.095825] Primary handler called for nested irq 348
>
> warnings on resume.
>
> Signed-off-by: NeilBrown <neil@brown.name>
>
> diff --git a/kernel/irq/pm.c b/kernel/irq/pm.c
> index 3ca532592704..40cbcfb7fc43 100644
> --- a/kernel/irq/pm.c
> +++ b/kernel/irq/pm.c
> @@ -118,6 +118,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);
> @@ -158,6 +160,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);
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-01-30 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 22:25 NeilBrown
2015-01-30 23:06 ` Rafael J. Wysocki [this message]
2015-01-30 23:51 ` Rafael J. Wysocki
2015-01-31 3:37 ` NeilBrown
2015-02-02 22:50 ` Rafael J. Wysocki
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=1465455.9L1ju05BhM@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=gta04-owner@goldelico.com \
--cc=kalle.jokiniemi@jollamobile.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=neilb@suse.de \
--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
all inboxes | Powered by JetHome®