From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Xen 4.5 development update Date: Wed, 28 May 2014 11:46:56 -0400 Message-ID: <20140528154656.GJ10363@phenom.dumpdata.com> References: <20140527180640.6053D1BF275@phenom.dumpdata.com> <5385B407.40503@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wpg4U-0005b3-RK for xen-devel@lists.xenproject.org; Wed, 28 May 2014 15:47:19 +0000 Content-Disposition: inline In-Reply-To: <5385B407.40503@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Cc: feng.wu@intel.com, ufimtseva@gmail.com, JBeulich@suse.com, daniel.kiper@oracle.com, zoltan.kiss@citrix.com, avanzini.arianna@gmail.com, xen-devel@lists.xenproject.org, olaf@aepfle.de, stefano.stabellini@eu.citrix.com, julien.grall@linaro.org, Paul.Durrant@citrix.com, msw@amazon.com, boris.ostrovsky@oracle.com, andrew.bennieston@citrix.com, Wei.Liu2@citrix.com, andrew.cooper3@citrix.com, Kelly.Zytaruk@amd.com, dslutz@verizon.com, david.vrabel@citrix.com, tiejun.chen@intel.com, malcolm.crossley@citrix.com List-Id: xen-devel@lists.xenproject.org On Wed, May 28, 2014 at 11:01:43AM +0100, Roger Pau Monn=E9 wrote: > On 27/05/14 19:06, konrad.wilk@oracle.com wrote: > > Below is a summary of the projects / features being worked on for the 4= .5 > > time frame that I had been gathering. > > = > > It is not complete! I would like folks input if I had missed something > > or screwed up. Will also talk at Xen Hackahon about this and take a look > > at http://wiki.xen.org/wiki/Xen_Roadmap/4.4 to see which of the > > items there should move over. > > = > > The tentative feature freeze is scheduled for September 10th, > > which is months away. With that in mind, I think it's time to take > > stock of the development, so we know whether to ask for more help or di= vert > > resources. > > = > > For items involving code hosted on the Xen.org site (including qemu-xen= ), > > that means a likelihood of having the feature code-complete and mostly > > working by the feature freeze. (It's OK if there are still bugs to be > > worked out.) For items in Linux, I think it would mean having items on= track > > to make it into the kernel released just after the scheduled 4.5 time f= rame. > > Not sure what that means for libvirt. :-) > > = > > For items involving code hosted on the Xen.org site (including qemu-xen= ), > > that means a likelihood of having the feature code-complete and mostly > > working by the feature freeze. (It's OK if there are still bugs to be > > worked out.) For items in Linux, I think it would mean having items on= track > > to make it into the kernel released just after the scheduled 4.5 time f= rame. > > Not sure what that means for libvirt. :-) > > = > > =3D Timeline =3D > > = > > We are planning on a 9-month release cycle. Based on that, below are > > our estimated dates: > > * Feature Freeze: 10th September 2014 > > * First RC: 10th October > > * Release: 10th December 2014 > > = > > The RCs and release will of course depend on stability and bugs, and > > will therefore be fairly unpredictable. The feature freeze may be > > slipped for especially important features which are near completion. > > = > > =3D Prognosis =3D > = > [...] > = > > * Roger Pau Monn=C3=A9 Prognosis: 100 % > > Xen PVH dom0 > > PVH FreeBSD dom0 > = > Hello Konrad, Hey! > = > Thanks for doing this list, I certainly think Xen PVH Dom0 will make it > to 4.5, most patches are already committed, and the remaining ones are > already reviewed AFAIK. So very soon we will have PVH Dom0 available on > Intel HW with EPT support, which brings the next question, what do we > think we should work on after that? There are a bunch of things still > pending for PVH, and I'm not sure we will be able to get all them done > for 4.5, here's a list on top of my head: > = > - PCI passthrough for DomU. > - Migration of PVH DomUs. > - Migration of guests from a PVH Dom0. > - AMD hardware support. > - PVH working with shadow. > = > IMHO, I think the two most important items would be getting PVH working > on AMD hardware and shadow, but maybe others have different opinions. I concur. I know that Mukesh had been in the time between reviews eyeballing the AMD part, but nothing concrete yet. I would say that the list of interesting/important items could be = in this order: - Migration of PVH DomUs. - Migration of guests from a PVH Dom0. - AMD hardware support (Mukesh). - PVH working with shadow. - PCI passthrough for DomU. But that is just my take. > = > Roger. > =