Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752092AbZL0N2Y (ORCPT ); Sun, 27 Dec 2009 08:28:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751924AbZL0N2W (ORCPT ); Sun, 27 Dec 2009 08:28:22 -0500 Received: from mx1.redhat.com ([209.132.183.28]:15630 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751874AbZL0N2V (ORCPT ); Sun, 27 Dec 2009 08:28:21 -0500 Message-ID: <4B3760D2.3080500@redhat.com> Date: Sun, 27 Dec 2009 15:27:46 +0200 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-4.fc12 Thunderbird/3.0 MIME-Version: 1.0 To: Gregory Haskins CC: Andi Kleen , kvm@vger.kernel.org, Bartlomiej Zolnierkiewicz , netdev@vger.kernel.org, "linux-kernel@vger.kernel.org" , "alacrityvm-devel@lists.sourceforge.net" , Anthony Liguori , Ingo Molnar , torvalds@linux-foundation.org, Andrew Morton Subject: Re: [Alacrityvm-devel] [GIT PULL] AlacrityVM guest drivers for 2.6.33 References: <4B1D4F29.8020309@gmail.com> <87637zdy9g.fsf@basil.nowhere.org> <4B30E654.40702@codemonkey.ws> <200912221701.56840.bzolnier@gmail.com> <4B30F214.80206@codemonkey.ws> <20091223065129.GA19600@elte.hu> <20091223101340.GC20539@basil.fritz.box> <4B31EF65.6070000@redhat.com> <4B325E33.8060407@gmail.com> <4B327B90.2050403@redhat.com> <4B3725CE.8040004@redhat.com> <4B375EAD.8050204@gmail.com> In-Reply-To: <4B375EAD.8050204@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1311 Lines: 33 On 12/27/2009 03:18 PM, Gregory Haskins wrote: > On 12/27/09 4:15 AM, Avi Kivity wrote: > >> On 12/23/2009 11:21 PM, Gregory Haskins wrote: >> >>> That said, you are still incorrect. With what I proposed, the model >>> will run as an in-kernel vbus device, and no longer run in userspace. >>> It would therefore improve virtio-net as I stated, much in the same >>> way vhost-net or venet-tap do today. >>> >>> >> That can't work. virtio-net has its own ABI on top of virtio, for >> example it prepends a header for TSO information. Maybe if you disable >> all features it becomes compatible with venet, but that cripples it. >> >> > You are confused. The backend would be virtio-net specific, and would > therefore understand the virtio-net ABI. It would support any feature > of virtio-net as long as it was implemented and negotiated by both sides > of the link. > Then we're back to square one. A nice demonstration of vbus flexibility, but no help for virtio. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/