mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Greg KH <greg@kroah.com>, "stable@kernel.org" <stable@kernel.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: longterm backport request: xen/timer: Missing IRQF_NO_SUSPEND in timer code broke suspend
Date: Mon, 17 Oct 2011 10:32:24 +0100	[thread overview]
Message-ID: <1318843944.16132.3.camel@zakaz.uk.xensource.com> (raw)

(resending since I suspect stable@ was down the first time round. Also I
should have CC'd Thomas & LKML, I think)

Hi Greg,

Please can you queue this commit for 3.6.32.y

        commit f611f2da99420abc973c32cdbddbf5c365d0a20c
        Author: Ian Campbell <Ian.Campbell@citrix.com>
        Date:   Tue Feb 8 14:03:31 2011 +0000
        
            xen/timer: Missing IRQF_NO_SUSPEND in timer code broke suspend.
            
            The patches missed an indirect use of IRQF_NO_SUSPEND pulled in via
            IRQF_TIMER. The following patch fixes the issue.
            
            With this fixlet PV guest migration works just fine. I also booted the
            entire series as a dom0 kernel and it appeared fine.
            
            Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
            Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

It is needed in any tree which contains 676dc3cf5bc3 "xen: Use
IRQF_FORCE_RESUME" but not this change (everything was fixed upstream in
2.6.39-rc1).

It's a bit hard to tell in the absence of kernel.org but I have an old
(but post February) checkout of the 2.6.35 longterm and it does not appear
to have the original problematic patch so the fix isn't needed there.
IOW AFAICT right now 2.6.32 seems to be the only relevant tree.

Thanks,
Ian.




                 reply	other threads:[~2011-10-17  9:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1318843944.16132.3.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=greg@kroah.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --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®