From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MEKR5-0003kC-Nf for qemu-devel@nongnu.org; Wed, 10 Jun 2009 05:49:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MEKR0-0003is-Ow for qemu-devel@nongnu.org; Wed, 10 Jun 2009 05:49:34 -0400 Received: from [199.232.76.173] (port=37205 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MEKR0-0003ii-Am for qemu-devel@nongnu.org; Wed, 10 Jun 2009 05:49:30 -0400 Received: from mx2.redhat.com ([66.187.237.31]:39206) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MEKQz-0001KI-Ow for qemu-devel@nongnu.org; Wed, 10 Jun 2009 05:49:30 -0400 Date: Wed, 10 Jun 2009 12:46:04 +0300 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] [PATCH 05/11] qemu: MSI-X support functions Message-ID: <20090610094604.GD6844@redhat.com> References: <20090525122541.GF5046@redhat.com> <200906100019.59981.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200906100019.59981.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: Carsten Otte , kvm@vger.kernel.org, Rusty Russell , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Blue Swirl , Christian Borntraeger , Avi Kivity On Wed, Jun 10, 2009 at 12:19:42AM +0100, Paul Brook wrote: > On Monday 25 May 2009, Michael S. Tsirkin wrote: > > Add functions implementing MSI-X support. First user will be virtio-pci. > > Note that platform must set a flag to declare MSI supported. > > For PC this will be set by APIC. > > This sounds wrong. The device shouldn't know or care whether the system has a > MSI capable interrupt controller. That's for the guest OS to figure out. > > Paul You are right of course. In theory there's nothing that breaks if I set this flag to on, on all platforms. OTOH if qemu emulates some controller incorrectly, guest might misdetect MSI support in the controller, and things will break horribly. It seems safer to have a flag that can be enabled by people that know about a specific platform. What do you think? -- MST