From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: linuxppc-dev@ozlabs.org, embedded-hypervisor@power.org,
hollisb@us.ibm.com, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0/6][RFC] kvmppc: paravirtualization interface
Date: Thu, 24 Jul 2008 10:17:31 +0200 [thread overview]
Message-ID: <48883A9B.3050608@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080724020112.GM20457@bakeyournoodle.com>
Tony Breeds wrote:
> On Wed, Jul 23, 2008 at 10:36:41AM +0200, ehrhardt@linux.vnet.ibm.com wrote:
>
>> From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
>>
>> 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.au http://www.marchsouth.org/
> Jan 19 - 24 2009 The Australian Linux Technical Conference!
>
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
next prev parent reply other threads:[~2008-07-24 8:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 8:36 [PATCH 0/6][RFC] kvmppc: paravirtualization interface ehrhardt
2008-07-23 8:36 ` [PATCH 1/6] kvmppc: read device tree hypervisor node infrastructure ehrhardt
2008-07-24 1:41 ` Tony Breeds
2008-07-24 7:44 ` Christian Ehrhardt
2008-07-23 8:36 ` [PATCH 2/6] kvmppc: add hypercall infrastructure - host part ehrhardt
2008-07-24 1:43 ` Tony Breeds
2008-07-30 13:41 ` Geert Uytterhoeven
2008-07-23 8:36 ` [PATCH 3/6] kvmppc: add hypercall infrastructure - guest part ehrhardt
2008-07-24 1:45 ` Tony Breeds
2008-07-24 7:56 ` Christian Ehrhardt
2008-07-23 8:36 ` [PATCH 4/6] kvmppc: magic page hypercall - host part ehrhardt
2008-07-24 1:49 ` Tony Breeds
2008-07-23 8:36 ` [PATCH 5/6] kvmppc: magic page paravirtualization - guest part ehrhardt
2008-07-24 1:59 ` Tony Breeds
2008-07-23 8:36 ` [PATCH 6/6] kvmppc: kvm-userspace: device tree modification for magicpage ehrhardt
2008-07-24 2:01 ` [PATCH 0/6][RFC] kvmppc: paravirtualization interface Tony Breeds
2008-07-24 8:17 ` Christian Ehrhardt [this message]
2008-07-25 1:08 ` Tony Breeds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48883A9B.3050608@linux.vnet.ibm.com \
--to=ehrhardt@linux.vnet.ibm.com \
--cc=embedded-hypervisor@power.org \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tony@bakeyournoodle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).