From: Avi Kivity Subject: Re: [Qemu-devel] Re: virtio-blk performance and MSI Date: Sun, 09 Aug 2009 20:49:23 +0300 Message-ID: <4A7F0C23.8070807@redhat.com> References: <20090806163549.GA25594@lst.de> <4A7E9E7F.2090901@redhat.com> <20090809174100.GA17096@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Christoph Hellwig Return-path: Received: from mx2.redhat.com ([66.187.237.31]:43872 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752373AbZHIRtA (ORCPT ); Sun, 9 Aug 2009 13:49:00 -0400 In-Reply-To: <20090809174100.GA17096@lst.de> Sender: kvm-owner@vger.kernel.org List-ID: On 08/09/2009 08:41 PM, Christoph Hellwig wrote: > On Sun, Aug 09, 2009 at 01:01:35PM +0300, Avi Kivity wrote: > >> Looks good. Anthony, I think this applies upstream? >> > > This applies upstream, but as mentioned we can't just use it as-is. > We'll very recent kvm kernel support for multiple MSI vectors, and > when the host doesn't have it even 2.6.30 crashes badly in the guest. > Sorry, confused. Upstream doesn't use kvm for msi (everything's done in userspace). What exactly blocks us here? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.