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 0/6] MSI-INTx interrupt translation for HVM

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/6] MSI-INTx interrupt translation for HVM
From: Qing He <qing.he@xxxxxxxxx>
Date: Mon, 2 Mar 2009 17:24:40 +0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Shohei Fujiwara <fujiwara-sxa@xxxxxxxxxxxxxxx>
Delivery-date: Mon, 02 Mar 2009 01:23:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C5D14DB9.3DB4%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: <20090302161339.8372.CB716985@xxxxxxxxxxxxxxx> <C5D14DB9.3DB4%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.17+20080114 (2008-01-14)
On Mon, 2009-03-02 at 16:47 +0800, Keir Fraser wrote:
> On 02/03/2009 07:19, "Shohei Fujiwara" <fujiwara-sxa@xxxxxxxxxxxxxxx> wrote:
> 
> > Today, I found the hypervisor issues EOI ASAP. So Qing's explanation
> > reflected the implementation of the hypervisor.
> > 
> > xen/drivers/passthrough/io.c:
> > void hvm_dirq_assist(struct vcpu *v)
> > {
> > ...
> >             if ( hvm_irq_dpci->mirq[irq].flags & HVM_IRQ_DPCI_TRANSLATE )
> >             {
> >                 /* for translated MSI to INTx interrupt, eoi as early as
> > possible */
> >                 __msi_pirq_eoi(d, irq);
> >             }
> 
> Ah, well the passthrough-specific logic is not something I'm so familiar
> with! That above code indeed doesn't look correct. :-)

I recently learned that some device may keep issuing MSI until it is explicitly
cleared by software. In that case it just behaves like level-triggered
interrupt, and doing something like the code above will cause interrupt storm.
This is reflected in cs. 19065.

Do you mean this issue?

Thanks,
Qing


> 
>  -- Keir
> 
> 

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