[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45D61C74.2000601@vmware.com>
Date: Fri, 16 Feb 2007 13:04:52 -0800
From: Zachary Amsden <zach@...are.com>
To: Christoph Lameter <clameter@....com>
CC: Jeremy Fitzhardinge <jeremy@...p.org>, Andi Kleen <ak@....de>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org,
xen-devel@...ts.xensource.com, Chris Wright <chrisw@...s-sol.org>
Subject: Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops
interface
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?
>
For the most part, it doesn't disturb VMware or KVM. Xen does need some
additional functionality in paravirt-ops because they took a different
design choice - direct page tables instead of shadow page tables. This
is where all the requirements for the new Xen paravirt-ops hooks come from.
Zach
-
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