Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965014AbXBQE7Y (ORCPT ); Fri, 16 Feb 2007 23:59:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965018AbXBQE7Y (ORCPT ); Fri, 16 Feb 2007 23:59:24 -0500 Received: from ozlabs.org ([203.10.76.45]:44529 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965014AbXBQE7X (ORCPT ); Fri, 16 Feb 2007 23:59:23 -0500 Subject: Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface From: Rusty Russell To: Christoph Lameter Cc: Jeremy Fitzhardinge , Chris Wright , Andi Kleen , xen-devel@lists.xensource.com, virtualization@lists.osdl.org, Andrew Morton , linux-kernel@vger.kernel.org, Ingo Molnar In-Reply-To: References: <20070216022449.739760547@goop.org> Content-Type: text/plain Date: Sat, 17 Feb 2007 15:58:18 +1100 Message-Id: <1171688298.18876.63.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1072 Lines: 24 On Fri, 2007-02-16 at 12:49 -0800, Christoph Lameter wrote: > On Thu, 15 Feb 2007, Jeremy Fitzhardinge wrote: > > > This patch series implements the Linux Xen guest in terms of the > > paravirt-ops interface. The features in implemented this patch series > > I am thoroughly confused. Maybe that is because I have not been following > this issue closely but it seems that you are using the paravirt interface > as an API for Xen code in the guest? I thought the idea of paravirt was to > have an API that is generic? This patchset seems to be mostly realizing > Xen specific functionality? How does the code here interact with KVM, > VMWare and other hypervisors? It doesn't. Paravirt_ops provides the hooks. KVM, lguest, VMI and Xen all need to implement what they want on top of them. Hope that clarifies, Rusty. - 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/