| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for
|
To: |
Christoph Lameter <clameter@xxxxxxx> |
|
Subject: |
[Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface |
|
From: |
Rusty Russell <rusty@xxxxxxxxxxxxxxx> |
|
Date: |
Sat, 17 Feb 2007 15:58:18 +1100 |
|
Cc: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Chris Wright <chrisw@xxxxxxxxxxxx>, Andi Kleen <ak@xxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx> |
|
Delivery-date: |
Fri, 16 Feb 2007 20:58:39 -0800 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<Pine.LNX.4.64.0702161244380.26718@xxxxxxxxxxxxxxxxxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<20070216022449.739760547@xxxxxxxx> <Pine.LNX.4.64.0702161244380.26718@xxxxxxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home