[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1171688298.18876.63.camel@localhost.localdomain>
Date: Sat, 17 Feb 2007 15:58:18 +1100
From: Rusty Russell <rusty@...tcorp.com.au>
To: Christoph Lameter <clameter@....com>
Cc: Jeremy Fitzhardinge <jeremy@...p.org>,
Chris Wright <chrisw@...s-sol.org>, Andi Kleen <ak@....de>,
xen-devel@...ts.xensource.com, virtualization@...ts.osdl.org,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>
Subject: Re: [patch 00/21] Xen-paravirt: Xen guest implementation for
paravirt_ops interface
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists