All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Bader <stefan.bader@canonical.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: Stable candidate? xen: events: do not unmask event channels on resume
Date: Tue, 07 Jun 2011 09:44:29 +0200	[thread overview]
Message-ID: <4DEDD6DD.9020304@canonical.com> (raw)

Resending. I could not see this going to the list, so I subscribed and am trying
again.

-Stefan

-------- Original Message --------
Subject: Stable candidate? xen: events: do not unmask event channels on resume
Date: Wed, 25 May 2011 16:46:47 +0200
From: Stefan Bader <stefan.bader@canonical.com>
To: xen-devel@lists.xensource.com <xen-devel@lists.xensource.com>
CC: Ian Campbell <ian.campbell@citrix.com>

The following patch was reported to solve (at least some in the .32 case) hangs
on migration for 2.6.32 and 2.6.35 based kernels. I am not completely sure about
the 2.6.32 case as some reporters were reporting success after it was applied,
others still had issues[1]. But at least it seemed to improve the situation.
Should this get proposed for upstream longterm trees?

-Stefan

>From cf2e26cf8402af6f65bd89611682497db278f309 Mon Sep 17 00:00:00 2001
From: Ian Campbell <ian.campbell@citrix.com>
Date: Mon, 1 Nov 2010 16:30:09 +0000
Subject: [PATCH] xen: events: do not unmask event channels on resume

[1] https://bugs.launchpad.net/ubuntu/maverick/+source/linux/+bug/681083

             reply	other threads:[~2011-06-07  7:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  7:44 Stefan Bader [this message]
2011-06-07  8:48 ` Stable candidate? xen: events: do not unmask event channels on resume Ian Campbell
2011-06-07  9:07   ` Stefan Bader
2011-06-07  9:14     ` Ian Campbell
2011-06-07 10:01       ` Stefan Bader
2011-06-07 10:23         ` Ian Campbell

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=4DEDD6DD.9020304@canonical.com \
    --to=stefan.bader@canonical.com \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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 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.