From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [Qemu-devel] Re: virtio-blk performance and MSI Date: Sun, 9 Aug 2009 21:13:13 +0200 Message-ID: <20090809191313.GA23446@lst.de> References: <20090806163549.GA25594@lst.de> <4A7E9E7F.2090901@redhat.com> <20090809174100.GA17096@lst.de> <4A7F0C23.8070807@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , Anthony Liguori , qemu-devel@nongnu.org, kvm@vger.kernel.org, "Michael S. Tsirkin" To: Avi Kivity Return-path: Received: from verein.lst.de ([213.95.11.210]:42562 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752003AbZHITNa (ORCPT ); Sun, 9 Aug 2009 15:13:30 -0400 Content-Disposition: inline In-Reply-To: <4A7F0C23.8070807@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Sun, Aug 09, 2009 at 08:49:23PM +0300, Avi Kivity wrote: > Sorry, confused. Upstream doesn't use kvm for msi (everything's done in > userspace). What exactly blocks us here? Hmm, good question. Michael, do you know if we can just enabled MSI unconditionally in upstream qemu, or are there guests that can't cope with it? From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MaDpZ-000691-G9 for qemu-devel@nongnu.org; Sun, 09 Aug 2009 15:13:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MaDpV-00066W-1i for qemu-devel@nongnu.org; Sun, 09 Aug 2009 15:13:21 -0400 Received: from [199.232.76.173] (port=46645 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MaDpU-00066T-Sw for qemu-devel@nongnu.org; Sun, 09 Aug 2009 15:13:16 -0400 Received: from verein.lst.de ([213.95.11.210]:49709) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1MaDpU-0000JK-IL for qemu-devel@nongnu.org; Sun, 09 Aug 2009 15:13:16 -0400 Date: Sun, 9 Aug 2009 21:13:13 +0200 From: Christoph Hellwig Subject: Re: [Qemu-devel] Re: virtio-blk performance and MSI Message-ID: <20090809191313.GA23446@lst.de> References: <20090806163549.GA25594@lst.de> <4A7E9E7F.2090901@redhat.com> <20090809174100.GA17096@lst.de> <4A7F0C23.8070807@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A7F0C23.8070807@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: kvm@vger.kernel.org, "Michael S. Tsirkin" , Christoph Hellwig , qemu-devel@nongnu.org On Sun, Aug 09, 2009 at 08:49:23PM +0300, Avi Kivity wrote: > Sorry, confused. Upstream doesn't use kvm for msi (everything's done in > userspace). What exactly blocks us here? Hmm, good question. Michael, do you know if we can just enabled MSI unconditionally in upstream qemu, or are there guests that can't cope with it?