All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.4 development update -- RFC for feature freeze timeline
Date: Fri, 27 Sep 2013 11:21:56 +0100	[thread overview]
Message-ID: <alpine.DEB.2.02.1309271121150.5498@kaball.uk.xensource.com> (raw)
In-Reply-To: <CAFLBxZZg782KP=O9JW9FORNGBvUs+p-1UcqsPvVgkMK46uN7KA@mail.gmail.com>

On Thu, 26 Sep 2013, George Dunlap wrote:
> Additional things which are likely to make it if we extend a month (18
> Nov):
> 
> * NUMA Memory migration
> * Per-vcpu NUMA affinity
> * PV NUMA interface
> * ARM guest migration
> * USB hotplug for libxl

* new hypercalls for SWIOTLB on ARM


> Nonetheless, it does seem likely that delaying for a month may allow a
> significant number of important features to get in.
> 
> Any thoughts?

+ 1 for delaying by one month

  parent reply	other threads:[~2013-09-27 10:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 16:47 Xen 4.4 development update -- RFC for feature freeze timeline George Dunlap
2013-09-26 17:24 ` Dario Faggioli
2013-09-27  6:21   ` Elena Ufimtseva
2013-09-27  7:38 ` Jan Beulich
2013-09-27  9:37   ` David Vrabel
2013-09-27  9:51     ` Jan Beulich
2013-09-27  7:41 ` Jan Beulich
2013-10-04 17:36   ` George Dunlap
2013-09-27 10:21 ` Stefano Stabellini [this message]
2013-10-08 18:05 ` Xen 4.4 development update, qemu pci hole start address Pasi Kärkkäinen
2013-10-08 18:13   ` Pasi Kärkkäinen
2013-10-09 10:39     ` George Dunlap
2013-11-11 18:17       ` Pasi Kärkkäinen
2013-09-27 11:52 Xen 4.4 development update -- RFC for feature freeze timeline Boris Ostrovsky
2013-10-04 15:59 ` George Dunlap
2013-10-07  4:59 유재용
2013-10-07  6:55 ` Jan Beulich
2013-10-07  9:53 ` George Dunlap
2013-10-07 10:45 Jaeyong Yoo
2013-10-07 10:49 유재용
2013-10-07 11:25 ` Ian Campbell

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=alpine.DEB.2.02.1309271121150.5498@kaball.uk.xensource.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.