From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936752AbXGSA60 (ORCPT ); Wed, 18 Jul 2007 20:58:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756473AbXGSA6S (ORCPT ); Wed, 18 Jul 2007 20:58:18 -0400 Received: from lemon.ertos.nicta.com.au ([203.143.174.143]:33787 "EHLO lemon.gelato.unsw.edu.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759352AbXGSA6R (ORCPT ); Wed, 18 Jul 2007 20:58:17 -0400 X-Greylist: delayed 2566 seconds by postgrey-1.27 at vger.kernel.org; Wed, 18 Jul 2007 20:58:17 EDT Date: Thu, 19 Jul 2007 10:15:17 +1000 Message-ID: <87sl7lgsfe.wl%peter@chubb.wattle.id.au> From: Peter Chubb To: Or Sagi CC: linux-kernel@vger.kernel.org, calebm@gelato.unsw.edu.au User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 MULE XEmacs/21.4 (patch 20) (Double Solitaire) (x86_64-linux-gnu) X-Face: GgFg(Z>fx((4\32hvXq<)|jndSniCH~~$D)Ka:P@e@JR1P%Vr}EwUdfwf-4j\rUs#JR{'h# !]])6%Jh~b$VA|ALhnpPiHu[-x~@<"@Iv&|%R)Fq[[,(&Z'O)Q)xCqe1\M[F8#9l8~}#u$S$Rm`S9% \'T@`:&8>Sb*c5d'=eDYI&GF`+t[LfDH="MP5rwOO]w>ALi7'=QJHz&y&C&TE_3j! Organization: Chubb Family (Sydney) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 203.143.174.121 X-SA-Exim-Mail-From: peterc@gelato.unsw.edu.au Subject: Re: [RFC] Deferred interrupt handling. X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:39:27 +0000) X-SA-Exim-Scanned: Yes (on lemon.gelato.unsw.edu.au) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org The problem you're having is essentially the same as the user-level interrupt handler problem I've been dealing with for ages. The basic rule is: don't share interrupts between devices on the host and devices in the guest. But you *can* share interrupts between devices in a single guest. If you want the code, see http://www.gelato.unsw.edu.au/cgi-bin/viewvc.cgi/cvs/kernel/usrdrivers/latest/ and look at generic-irq.patch and fasync (which adds asynchronous notifications) For the KVM work it'll need modifying a little, but the basic infrastructure is there. We've currently got this working to pass interrupts to a type-II (hosted) virtual machine monitor running a guest kernel with native drivers. -- Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au http://www.ertos.nicta.com.au ERTOS within National ICT Australia