![]() | |||||||||||
Messages in this thread
|
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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2007-02-16 22:07 [from the cache] ©2003-2008 | |||||||||||