From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 2/6] virtio_config Date: Sat, 22 Sep 2007 15:03:33 +0200 Message-ID: <46F512A5.90506@qumranet.com> References: <1190289808.7262.223.camel@localhost.localdomain> <1190290140.7262.228.camel@localhost.localdomain> <1190290369.7262.231.camel@localhost.localdomain> <46F26958.4080102@qumranet.com> <46F26DC7.9040001@qumranet.com> <1190339435.19451.23.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , lguest , virtualization To: Rusty Russell Return-path: In-Reply-To: <1190339435.19451.23.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Rusty Russell wrote: >> >> A side effect of this is that Xen drivers can no longer use virtio. >> > > I'm not so sure. > > We were always assuming that Xen could do state management in its virtio > layer. If this is not true, it implies we need hooks in the virtio > drivers, and I don't think we've made it worse by making it translate > xenbus config info into virtio_config. > This means writing a low-level ABI in terms of a high level API. And while that describes virtualization fairly will, I prefer not to do this more than strictly necessary. However, this can be rewritten if/when Xen or VMware show interest in porting their drivers to virtio. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/