From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M8DR1-000361-Eq
	for qemu-devel@nongnu.org; Sun, 24 May 2009 09:08:15 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M8DQw-000343-Nf
	for qemu-devel@nongnu.org; Sun, 24 May 2009 09:08:15 -0400
Received: from [199.232.76.173] (port=33940 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M8DDA-0005uN-PM
	for qemu-devel@nongnu.org; Sun, 24 May 2009 08:53:56 -0400
Received: from mx2.redhat.com ([66.187.237.31]:44567)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1M8Bgl-0007EA-SX
	for qemu-devel@nongnu.org; Sun, 24 May 2009 07:16:24 -0400
Message-ID: <4A192C06.3070603@redhat.com>
Date: Sun, 24 May 2009 14:14:14 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] qemu: msi irq allocation api
References: <20090520162130.GA22109@redhat.com>	<200905211423.20843.paul@codesourcery.com>	<20090521134650.GI25309@redhat.com>	<200905211453.14691.paul@codesourcery.com>
	<20090521140711.GJ25309@redhat.com>
In-Reply-To: <20090521140711.GJ25309@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Carsten Otte <cotte@de.ibm.com>, kvm@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Christian Borntraeger <borntraeger@de.ibm.com>, Paul Brook <paul@codesourcery.com>

Michael S. Tsirkin wrote:
> kvm needs data on MSI entries: that's the interface
> current kernel exposes for injecting these interrupts.
>
> I think we also need to support in-kernel devices which
> would inject MSI interrupt directly from kernel.
> For these, kvm would need to know when mask bit changes
> and give us info on pending bit.
>
> That's a fair amount of PCI specific code in kvm

My plan is to get rid of it.  The mask stuff need not be pci specific.

-- 
error compiling committee.c: too many arguments to function