WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] xen: don't leak IRQs over suspend/resume.

To: Jan Beulich <JBeulich@xxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xen: don't leak IRQs over suspend/resume.
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 02 Dec 2009 09:01:00 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 02 Dec 2009 01:01:32 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B1637CA0200007800022FB5@xxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcpzLDXfVDqNKUL0RYyqS8HGG+AtvgAAcHUD
Thread-topic: [Xen-devel] [PATCH] xen: don't leak IRQs over suspend/resume.
User-agent: Microsoft-Entourage/12.23.0.091001
On 02/12/2009 08:47, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

>> Fix this by changing unbind_from_irq() to handle teardown of interrupts which
>> have type!=IRQT_UNBOUND but are not currently bound to a specific event
>> channel.
> 
> This seems applicable to the 2.6.18/.27 trees too, doesn't it?

Pv_ops' IRQ/evtchn handling is quite different from .18/27's. The latter
don't have this issue -- we'd have noticed long ago if they did!

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel