All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@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: Thu, 26 Sep 2013 19:24:36 +0200	[thread overview]
Message-ID: <1380216276.2956.24.camel@Solace> (raw)
In-Reply-To: <CAFLBxZZg782KP=O9JW9FORNGBvUs+p-1UcqsPvVgkMK46uN7KA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1513 bytes --]

On gio, 2013-09-26 at 17:47 +0100, George Dunlap wrote:
> Additional things which are likely to make it if we extend a month (18
> Nov):
> 
> * NUMA Memory migration
>
Yep, I confirm: 18 Nov => probable. 18 Oct => no way. :-(

> * Per-vcpu NUMA affinity
>
This may make it by 18 Oct too. 18 Nov, I'm positive it'll be in.

> * PV NUMA interface
>
It's worth wait for Elena to comment on this, but (as said on IRC) I'm
quite sure there's no way this can make it by 18 Oct.

> Other things that are a possibility if we slip a month but definitely
> not if we stick with the original schedule:
> 
> * qemu-xen stubdomains (either Linux or rump kernel / BSD libc)
>
Which would be something really cool to have on the release notes,
especially the rump kernel variant. ;-P

> 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 1 month.

I think it's probably worth to mention that we have LinuxConEU and
XenSummit coming (and just had LinuxConNA), for which people need to
prepare and attend, which would probably mean even less
developing/reviewing time for getting stuff in by 18 Oct.

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-09-26 17:24 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 [this message]
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
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=1380216276.2956.24.camel@Solace \
    --to=dario.faggioli@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.