From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] [PATCH] qemu: msi irq allocation api Date: Sun, 24 May 2009 14:14:14 +0300 Message-ID: <4A192C06.3070603@redhat.com> References: <20090520162130.GA22109@redhat.com> <200905211423.20843.paul@codesourcery.com> <20090521134650.GI25309@redhat.com> <200905211453.14691.paul@codesourcery.com> <20090521140711.GJ25309@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Paul Brook , Carsten Otte , kvm@vger.kernel.org, Rusty Russell , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Christian Borntraeger To: "Michael S. Tsirkin" Return-path: Received: from mx2.redhat.com ([66.187.237.31]:40187 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751520AbZEXLQY (ORCPT ); Sun, 24 May 2009 07:16:24 -0400 In-Reply-To: <20090521140711.GJ25309@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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