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] Interrupt forwarding

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Interrupt forwarding
From: Jon Smirl <jonsmirl@xxxxxxxxx>
Date: Sat, 12 Mar 2005 13:59:15 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, ian.pratt@xxxxxxxxxxxx
Delivery-date: Sat, 12 Mar 2005 19:01:08 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=MIxmh9cG5mXSQj25Yv3nxUvvOpNJj3QxVl+XhdxoRxXtJ2cCQMA6u615gWTGTSiabuFHLky+JfEw51F/0i0q5T4WSR2txjWtFX+kwOmYR9HmypwM3avjQIGNj1KYafvmaEGyimzDD/F/s6vwQgXELzzIcwZaqkfiysFF6hBQ7ZE=
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <f7ad8bba837b5b01bf13f789a612118f@xxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3602@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <d10e560f7d2d0190ed351d1955f129c5@xxxxxxxxxxxx> <9e47339105031210332d8756f0@xxxxxxxxxxxxxx> <f7ad8bba837b5b01bf13f789a612118f@xxxxxxxxxxxx>
Reply-to: Jon Smirl <jonsmirl@xxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
On Sat, 12 Mar 2005 18:48:53 +0000, Keir Fraser
<Keir.Fraser@xxxxxxxxxxxx> wrote:
> We don't go that far. A sensible approach would be to require the
> driver to be restarted, and to reset the hardware device, before
> unmasking. Or to rate limit each interrupt line to an

Have you tried cycling the cards to suspend S0 (power off) as a way of
clearing the interrupt?

-- 
Jon Smirl
jonsmirl@xxxxxxxxx


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel