From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NHeO5-00018z-0T for qemu-devel@nongnu.org; Mon, 07 Dec 2009 09:16:29 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NHeO0-00018E-8s for qemu-devel@nongnu.org; Mon, 07 Dec 2009 09:16:28 -0500 Received: from [199.232.76.173] (port=47265 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NHeO0-00018B-1K for qemu-devel@nongnu.org; Mon, 07 Dec 2009 09:16:24 -0500 Received: from mx1.redhat.com ([209.132.183.28]:13324) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NHeNz-0001PE-Ud for qemu-devel@nongnu.org; Mon, 07 Dec 2009 09:16:24 -0500 Date: Mon, 7 Dec 2009 16:13:39 +0200 From: "Michael S. Tsirkin" Message-ID: <20091207141339.GC5328@redhat.com> References: <1259137008-9669-1-git-send-email-kraxel@redhat.com> <1259137008-9669-2-git-send-email-kraxel@redhat.com> <20091207093716.GA31370@redhat.com> <4B1CD9C4.4020509@redhat.com> <20091207105950.GA3376@redhat.com> <4B1CE5D2.5080205@redhat.com> <20091207130329.GA3937@redhat.com> <4B1D0031.20705@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B1D0031.20705@redhat.com> Subject: [Qemu-devel] Re: [PATCH 2/2] virtio: enable msi-x for console+balloon List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: qemu-devel@nongnu.org On Mon, Dec 07, 2009 at 02:16:33PM +0100, Gerd Hoffmann wrote: > On 12/07/09 14:03, Michael S. Tsirkin wrote: >> Also - why not simply use virtio? I assume you are talking about >> guests with virtio support otherwise MSI support in virtio >> won't matter for them. > > Point. Guests with virtio-console+balloon most likely can use virtio > for storage+net too, so nothing performance-critical is left in ioapic > irq space and IRQ sharing for the leftovers (just usb I think) shouldn't > be a big issue. > >>> Yes. Three for balloon, but that can easily changed to two. >> >> Yes, please, make this change for 0.12. > > We can also simply drop this ... > >> No, but changing this will need updating guests. > > ... or postphone until we have the "one MSI-X vector" support working. OK. Anthony, could you drop this from staging for now please? Gerd, any idea whether "one MSI-X vector" feature is worth pursuing? -- MST