From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MEOxW-0000bN-3i for qemu-devel@nongnu.org; Wed, 10 Jun 2009 10:39:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MEOxQ-0000Iy-Kf for qemu-devel@nongnu.org; Wed, 10 Jun 2009 10:39:21 -0400 Received: from [199.232.76.173] (port=53801 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MEOxQ-0000Hf-Bh for qemu-devel@nongnu.org; Wed, 10 Jun 2009 10:39:16 -0400 Received: from mx20.gnu.org ([199.232.41.8]:57976) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MEOxQ-0006b5-33 for qemu-devel@nongnu.org; Wed, 10 Jun 2009 10:39:16 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MEOxP-0002U0-DW for qemu-devel@nongnu.org; Wed, 10 Jun 2009 10:39:15 -0400 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH 05/11] qemu: MSI-X support functions Date: Wed, 10 Jun 2009 15:39:05 +0100 References: <200906101507.39823.paul@codesourcery.com> <20090610142508.GA28409@redhat.com> In-Reply-To: <20090610142508.GA28409@redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906101539.12367.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Carsten Otte , kvm@vger.kernel.org, Rusty Russell , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Blue Swirl , Christian Borntraeger , Avi Kivity > > If we really need to avoid MSI-X capable devices then that should be done > > explicity per-device. i.e. you have a different virtio-net device that > > does not use MSI-X. > > > > Paul > > Why should it be done per-device? Because otherwise you end up with the horrible hacks that you're currently tripping over: devices have to magically morph into a different device when you load a VM. That's seems just plain wrong to me. Loading a VM shouldn't not do anything that can't happen during normal operation. Paul