From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?euc-kr?B?wK/A57/r?= Subject: Re: Xen 4.4 development update -- RFC for feature freeze timeline Date: Mon, 07 Oct 2013 04:59:03 +0000 (GMT) Message-ID: <26102985.223941381121941801.JavaMail.weblogic@epml19> Reply-To: jaeyong.yoo@samsung.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: MIME-version: 1.0 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini , George Dunlap Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org > 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 I have a question regarding the candidate features for feature freeze. Can anyone declare a new feature or does it only for Citrix employees and maintainers? For instance, if I want to upstream live migration feature in ARM, what am I going to do? > > > > > > > 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 >