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

[Xen-devel] RE: [PATCH] Handle MSI irq storm

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Subject: [Xen-devel] RE: [PATCH] Handle MSI irq storm
From: "Shan, Haitao" <haitao.shan@xxxxxxxxx>
Date: Fri, 4 Jul 2008 15:22:04 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 04 Jul 2008 00:22:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C4929001.2381C%keir.fraser@xxxxxxxxxxxxx>
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: <823A93EED437D048963A3697DB0E35DE017FDB5D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C4929001.2381C%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acjcy8F+D4qxw0AnTb6V8UsSMvI8BwAGIrDfAABHUbAAAdev+QAIDYLgAACKzNsAJa7SsA==
Thread-topic: [PATCH] Handle MSI irq storm
Hi, Keir,

This is updated patch. Please help review it. Thanks!

Best Regards
Haitao Shan

-----Original Message-----
From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx] 
Sent: 2008年7月3日 21:18
To: Shan, Haitao
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [PATCH] Handle MSI irq storm

On 3/7/08 14:12, "Shan, Haitao" <haitao.shan@xxxxxxxxx> wrote:

> As I was writing the new patch, I had some other considerations.
> Concerning PV guests, we can depend on the event-channel-pending to decide
> whether we will set timer and rely on the timer to enable this vector some
> time later.
> So for HVM guest, can we also rely on the timer to enable this interrupt
> vector later? (so in hvm_eoi_function, we only unmark the IRQ_INPROGRESS
> without enable it.) Thus, the handling can be the same for both PV guests and
> HVM guests.
> How do you think of this scheme?

Yes, that's exactly what I was thinking.

 -- Keir


Attachment: mask_second_edge_irq.patch
Description: mask_second_edge_irq.patch

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