public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Tony Breeds <tony@bakeyournoodle•com>
To: Christian Ehrhardt <ehrhardt@linux•vnet.ibm.com>
Cc: linuxppc-dev@ozlabs•org, hollisb@us•ibm.com, kvm-ppc@vger•kernel.org
Subject: Re: [PATCH 0/6][RFC] kvmppc: paravirtualization interface
Date: Fri, 25 Jul 2008 11:08:36 +1000	[thread overview]
Message-ID: <20080725010835.GQ20457@bakeyournoodle.com> (raw)
In-Reply-To: <48883A9B.3050608@linux.vnet.ibm.com>

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.au    http://www.marchsouth.org/
  Jan 19 - 24 2009 The Australian Linux Technical Conference!

      reply	other threads:[~2008-07-25  1:08 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
2008-07-25  1:08     ` Tony Breeds [this message]

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=20080725010835.GQ20457@bakeyournoodle.com \
    --to=tony@bakeyournoodle$(echo .)com \
    --cc=ehrhardt@linux$(echo .)vnet.ibm.com \
    --cc=hollisb@us$(echo .)ibm.com \
    --cc=kvm-ppc@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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