From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: <stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [34-longterm 074/179] xen: Use IRQF_FORCE_RESUME
Date: Tue, 15 May 2012 12:33:16 -0400 [thread overview]
Message-ID: <20120515163316.GC17760@windriver.com> (raw)
In-Reply-To: <20120515050221.GA4292@burratino>
[Re: [34-longterm 074/179] xen: Use IRQF_FORCE_RESUME] On 15/05/2012 (Tue 00:02) Jonathan Nieder wrote:
> Hi Paul,
>
> Paul Gortmaker wrote:
>
> > From: Thomas Gleixner <tglx@linutronix.de>
> [...]
> > If you see a problem with using this for longterm, please comment.
> [...]
> > commit 676dc3cf5bc36a9e129a3ad8fe3bd7b2ebf20f5d upstream.
> >
> > Mark the IRQF_NO_SUSPEND interrupts IRQF_FORCE_RESUME and remove the extra
> > walk through the interrupt descriptors.
>
> This produces resume failures and migration failures in Xen guests[1].
>
> Commit 9bab0b7fbace (genirq: Add IRQF_RESUME_EARLY and resume such
> IRQs earlier, 2011-11-09) is needed on top to avoid regressions.
>
> Hope that helps,
> Jonathan
>
> [1] http://thread.gmane.org/gmane.linux.kernel/1198673
Hi Jonathan,
I'd considered this patch, but then saw Greg used it on 2.6.32
and reverted it one release later:
-------------------
commit 758d61b4a76e6ad4224780771edbc6d3a0c29b16
Author: Greg Kroah-Hartman <gregkh@suse.de>
Date: Tue Nov 8 15:40:42 2011 -0800
Revert "genirq: Add IRQF_RESUME_EARLY and resume such IRQs earlier"
This reverts commit 0f12a6ad9fa3a03f2bcee36c9cb704821e244c40.
It causes too many build errors and needs to be done properly.
Reported-by: Jiri Slaby <jslaby@suse.cz>
Reported-by: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
Cc: Ian Campbell <ian.campbell@citrix.com>
[...]
-------------
What I didn't realize was that it got re-added as a v2 again in:
-------------
commit 5e87d8ee34e32fda720f3a4e4055f570b09230d6
Author: Ian Campbell <ian.campbell@citrix.com>
Date: Wed Nov 9 08:53:09 2011 +0000
genirq: Add IRQF_RESUME_EARLY and resume such IRQs earlier
[...]
Back ported to 2.6.32 (which lacks syscore support) by calling the relavant
resume function directly from sysdev_resume).
v2: Fixed non-x86 build errors.
-----------
I'll make sure the v2 ends up in the 34 queue.
Thanks again,
Paul.
prev parent reply other threads:[~2012-05-15 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1337048075-6132-1-git-send-email-paul.gortmaker@windriver.com>
2012-05-15 3:01 ` [34-longterm 000/179] v2.6.34.12 longterm review Paul Gortmaker
[not found] ` <1337048075-6132-168-git-send-email-paul.gortmaker@windriver.com>
[not found] ` <alpine.LSU.2.00.1205142126180.2196@eggly.anvils>
[not found] ` <1337079117.27694.28.camel@twins>
2012-05-15 16:02 ` [34-longterm 167/179] futex: Fix regression with read only mappings Paul Gortmaker
2012-05-15 18:55 ` Willy Tarreau
[not found] ` <1337048075-6132-180-git-send-email-paul.gortmaker@windriver.com>
[not found] ` <20120515154455.39cfbad2@pyramind.ukuu.org.uk>
[not found] ` <20120515154743.04879bde@pyramind.ukuu.org.uk>
2012-05-15 16:03 ` [34-longterm 179/179] x86/PCI: do not tie MSI MS-7253 use_crs quirk to BIOS version Paul Gortmaker
[not found] ` <1337048075-6132-75-git-send-email-paul.gortmaker@windriver.com>
[not found] ` <20120515050221.GA4292@burratino>
2012-05-15 16:33 ` Paul Gortmaker [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=20120515163316.GC17760@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).