Re: [PATCH 0/6][RFC] kvmppc: paravirtualization interface
Tony Breeds wrote: On Wed, Jul 23, 2008 at 10:36:41AM +0200, [EMAIL PROTECTED] wrote: From: Christian Ehrhardt [EMAIL PROTECTED] This patch series implements a paravirtualization interface using: - the device tree mechanism to pass hypervisor informations to the guest - hypercalls for guest-host calls - an example exploiter of that interface (magic page) This is work in progress, but working so far. I just start to really exploit the fuctionality behind the magic page mechanism therefor I can't provide any performance improvements so far, but it is evolved enough for RFC and to start the standardization discussion. Are you aiming this for the current merge window, ie for 2.6.27? The aim is not really fixed. It would be nice to get into 2.6.27, but since I can't yet expect how long it takes ... Actually the guest patches would already go through reviews and upstream, due to the fact that the guest code changes are not that (the major part of the implementation will go over kvmppc - kvm upstream). But since I want to discuss about the standardization on the embedded hypervisor list first, the naming of the device tree entries are not fixed yet. Therefor I can't yet define which kernel version merge window I'll target/reach. btw - embedded hypervisor - I got advised that this is a closed list which I forgot. Sorry for all who got bounces on a replay-all action. The next version of the patch series will go to the involved open source lists only and a separate more standardization than patch style mail series to embedded hypervisor. Yours Tony linux.conf.auhttp://www.marchsouth.org/ Jan 19 - 24 2009 The Australian Linux Technical Conference! -- Grüsse / regards, Christian Ehrhardt IBM Linux Technology Center, Open Virtualization ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH 0/6][RFC] kvmppc: paravirtualization interface
On Thu, Jul 24, 2008 at 10:17:31AM +0200, Christian Ehrhardt wrote: The aim is not really fixed. It would be nice to get into 2.6.27, but since I can't yet expect how long it takes ... Ahh okay, Id say given that we're 2/3rds through the merge window then 2.8.28 is a safer target. Actually the guest patches would already go through reviews and upstream, due to the fact that the guest code changes are not that (the major part of the implementation will go over kvmppc - kvm upstream). But since I want to discuss about the standardization on the embedded hypervisor list first, the naming of the device tree entries are not fixed yet. Okay. When that's done we can take another look at them. Therefor I can't yet define which kernel version merge window I'll target/reach. btw - embedded hypervisor - I got advised that this is a closed list which I forgot. ... snipped from this reply Yours Tony linux.conf.auhttp://www.marchsouth.org/ Jan 19 - 24 2009 The Australian Linux Technical Conference! ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [PATCH 0/6][RFC] kvmppc: paravirtualization interface
On Wed, Jul 23, 2008 at 10:36:41AM +0200, [EMAIL PROTECTED] wrote: From: Christian Ehrhardt [EMAIL PROTECTED] This patch series implements a paravirtualization interface using: - the device tree mechanism to pass hypervisor informations to the guest - hypercalls for guest-host calls - an example exploiter of that interface (magic page) This is work in progress, but working so far. I just start to really exploit the fuctionality behind the magic page mechanism therefor I can't provide any performance improvements so far, but it is evolved enough for RFC and to start the standardization discussion. Are you aiming this for the current merge window, ie for 2.6.27? Yours Tony linux.conf.auhttp://www.marchsouth.org/ Jan 19 - 24 2009 The Australian Linux Technical Conference! ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
