From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MaCW4-0006lV-Fv
	for qemu-devel@nongnu.org; Sun, 09 Aug 2009 13:49:08 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MaCVz-0006l7-2S
	for qemu-devel@nongnu.org; Sun, 09 Aug 2009 13:49:07 -0400
Received: from [199.232.76.173] (port=54347 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MaCVy-0006l4-Ts
	for qemu-devel@nongnu.org; Sun, 09 Aug 2009 13:49:02 -0400
Received: from mx20.gnu.org ([199.232.41.8]:41851)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <avi@redhat.com>) id 1MaCVy-00027Y-BR
	for qemu-devel@nongnu.org; Sun, 09 Aug 2009 13:49:02 -0400
Received: from mx2.redhat.com ([66.187.237.31])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1MaCVw-0005Bu-Lz
	for qemu-devel@nongnu.org; Sun, 09 Aug 2009 13:49:01 -0400
Message-ID: <4A7F0C23.8070807@redhat.com>
Date: Sun, 09 Aug 2009 20:49:23 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: virtio-blk performance and MSI
References: <20090806163549.GA25594@lst.de> <4A7E9E7F.2090901@redhat.com>
	<20090809174100.GA17096@lst.de>
In-Reply-To: <20090809174100.GA17096@lst.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org

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.