This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: Stable candidate? xen: events: do not unmask event c

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Re: Stable candidate? xen: events: do not unmask event channels on resume
From: Stefan Bader <stefan.bader@xxxxxxxxxxxxx>
Date: Tue, 07 Jun 2011 11:07:46 +0200
Delivery-date: Tue, 07 Jun 2011 02:08:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1307436486.775.499.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4DEDD6DD.9020304@xxxxxxxxxxxxx> <1307436486.775.499.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10
On 07.06.2011 10:48, Ian Campbell wrote:
> On Tue, 2011-06-07 at 08:44 +0100, Stefan Bader wrote:
>> Resending. I could not see this going to the list, so I subscribed and am 
>> trying
>> again.
> Posts from non-subscribers are moderated, it would have come through at
> some point.
I was not sure how long that would take or whether non-subscribers would just
get dropped to prevent spam. It does not hurt to be subscribed, so discussion
can go quicker.

>> -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@xxxxxxxxxxxxx>
>> To: xen-devel@xxxxxxxxxxxxxxxxxxx <xen-devel@xxxxxxxxxxxxxxxxxxx>
>> CC: Ian Campbell <ian.campbell@xxxxxxxxxx>
>> 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
> This seems to be 6903591f314b in the upstream tree. Also there was a
> subsequent cleanup in 676dc3cf5bc3 which relies on dc5f219e, which we
> should consider too. I think as a set they make sense for a
> stable/longterm backport so you can have my:
> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
> for forwarding to stable@
> I expect you'll want/need tglx's Ack for the latter two as well.
They would be needed when trying to push the whole set, yes. On the other hand,
on a casual glance, these just seem to make some functionality that the first
patch did on the xen side, available in the generic framework.
If there is no issue without the two, my feeling would be, that going with the
single patch for stable/longterm would be better. To me things going there
should have a real functional benefit.
But probably I am overlooking something in the cleanup.


> Ian.
>> From: Ian Campbell <ian.campbell@xxxxxxxxxx>
>> 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
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list