From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Xen 4.5 development update (July update) Date: Wed, 3 Sep 2014 12:58:33 +0100 Message-ID: <54070269.2020004@citrix.com> References: <20140902204500.D39D0DC99F@laptop.dumpdata.com> <540635D1.1070403@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8021963462783568287==" Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XP9D8-0006mv-Bu for xen-devel@lists.xenproject.org; Wed, 03 Sep 2014 11:58:50 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: rshriram@cs.ubc.ca Cc: artem.mygaiev@globallogic.com, msw@amazon.com, ian.jackson@eu.citrix.com, Steve.VanderLeest@dornerworks.com, dongxiao.xu@intel.com, mengxu@cis.upenn.edu, chao.p.peng@linux.intel.com, feng.wu@intel.com, zhigang.x.wang@oracle.com, parth.dixit@linaro.org, boris.ostrovsky@oracle.com, P.aul.Skentzos@dornerworks.com, vijay.kilari@gmail.com, rcojocaru@bitdefender.com, guijianfeng@cn.fujitsu.com, daniel.kiper@oracle.com, stefano.stabellini@eu.citrix.com, josh.whitehead@dornerworks.com, zoltan.kiss@citrix.com, avanzini.arianna@gmail.com, anthony.perard@citrix.com, xen-devel@lists.xenproject.org, serge.broslavsky@linaro.org, yjhyun.yoo@samsung.com, olaf@aepfle.de, ian.campbell@citrix.com, wency@cn.fujitsu.com, mcgrof@suse.com, julien.grall@linaro.org, dave.scott@citrix.com, robert.vanvossen@dornerworks.com, shantong.kang@intel.com, roy.franz@linaro.org, yang.z.zhang@intel.comP List-Id: xen-devel@lists.xenproject.org --===============8021963462783568287== Content-Type: multipart/alternative; boundary="------------060809020508080103080009" --------------060809020508080103080009 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On 03/09/14 12:53, Shriram Rajagopalan wrote: > > Andrew, > > On Sep 2, 2014 5:29 PM, "Andrew Cooper" > wrote: > > > > On 02/09/2014 21:45, konrad.wilk@oracle.com > wrote: > > > Below is a summary of the projects / features being worked on for > the 4.5 > > > time frame. The tentative feature freeze is scheduled for > September 10th, > > > which is less a week away! > > > > > > Most of the Xen patches that impacted the hypervisor and had'fair' > > > (except the HVM introspection one) I moved to the Xen 4.6 list. > > > > > > They might get Acked by maintainers in the next couple of days > which would > > > be fantastic - and if so I will update the list. But perhaps not. Also > > > some are in 'good' or in 'ok' condition - but that does not mean they > > > will automatically go in Xen 4.5. > > > > > > In terms of QEMU - I only had three items and since the version > of QEMU > > > from upstream we are using is already established (and stable) I > don't see us > > > backporting any more patches from upstream. But perhaps Stefano > has some > > > other plans... > > > > > > In terms of the toolstack - I kept the ones that are in the 'fair' > category > > > as I think they are easier to test/rebase/retest than the > hypervisor ones. > > > > > > In terms of Linux I am keeping the 'fair' ones as by the Xen 4.6 > release > > > it could be v3.19, which means there is still an upcoming merge window > > > for those. > > > > > > The "prognosis" is now the likelihood of completion in the 4.5 > timeframe. > > > A bunch of items had moved to the completed phase which is fantastic. > > > > > > none - nothing yet > > > fair - still working on it, patches are prototypes or RFC > > > ok - patches posted, acting on review > > > good - some last minute pieces > > > done - all done, might have bugs > > > > > > 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, it would mean having items on track > > > to make it into the kernel released just after the scheduled 4.5 > time frame. > > > > > > In terms of libvirt it has monthly releases. As such not going to > track > > > every release - but closer to when RCs are out. > > > > > > = Timeline = > > > > > > We are planning on a 9-month release cycle. Based on that, below are > > > our estimated dates: > > > > > > * Coding time: <=== NOW, one week left! > > > > > > * 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. > > > > > > If you think your patchset MUST go in Xen 4.5 I will post the > procedure > > > for requesting an exception to get them in past the feature freeze > next > > > week. > > > > > > = Prognosis = > > > > > > The states are: none -> fair -> ok -> good -> done > > > > > > none - nothing yet > > > fair - still working on it, patches are prototypes or RFC > > > ok - patches posted, acting on review > > > good - some last minute pieces > > > done - all done, might have bugs > > > > > > > > > = Open = > > > > > > == ARM == > > > > > > * ARM - Device assigment on ARM (good) > > > Linux parts at risk. > > > v2 for hypervisor out > > > - Julien Grall > > > > > > * ARM XEN_DOMCTL_memory_mapping hypercall for ARM (good) > > > v12 posted. > > > - Arianna Avanzini > > > > > > * ARM Xen UEFI booting on ARM (ok) > > > v2 > > > - Roy Franz > > > > > > * ARM PSCI v0.2 (good) > > > v11 posted > > > - Parth Dixit > > > > > > * ARM GICv3 support (ok) > > > v6a patchset (refactor in, also known as v9a); v7 posted > > > v9a posted which does GIC and VGIC code refactoring > > > v8 posted > > > - Vijay Kilari > > > > > > * ARM - MiniOS (ok) > > > v7 posted > > > - Thomas Leonard > > > > > > * ARM - VGIC emulation (ok) > > > Reposted as gic and vgic fixes and improvements > > > v12 > > > - Stefano Stabellini > > > > > > * ARM - XENFEAT_grant_map_11 (aka map grants refs at pfn = mfn) (ok) > > > Provide kernels an grant->MFN lookup > > > v4 > > > - Stefano Stabellini > > > > > > * ARM - Add Odroid-XU (Exynos5410) support (ok) > > > v4 > > > - Suriyan Ramasami > > > > > > * ARM implement mem_access (ok) > > > v3 > > > https://github.com/tklengyel/xen/tree/arm_memaccess3 > > > - Tamas K Lengyel > > > > > > == x86 == > > > > > > * New Migration (v2). (good) > > > v6 posted, going on the 'good' side! > > > - Andrew Cooper & David Vrabel > > > > Work on the {lib,}xl side of things are making progress. > > > > Given the lack of stream versioning, *even* at the libxl level, both > > sets of changes need to go in together, so there is no chance of > > deferring the libxl work. > > > > PV is working and HVM is getting there. Currently have a lot of > > compatibility hacks until Wei's domain json series gets accepted (or > > cherrypicked into my queue). Also, making the restore side asynchronous > > is proving very difficult. > > > > Will also require some careful integration with remus. I believe my > > libxc series now contains all the remus-specific bugfixes discovered, > > but I have yet to have feedback. > > > > Sorry about this. Can you point me to the specific patches that you > need feedback on? > > Shriram > http://xenbits.xen.org/gitweb/?p=people/andrewcoop/xen.git;a=shortlog;h=refs/heads/saverestore2-v6.2 should contain all the underlying bugfixes identified from the remus libxc patch series. It also contains a few new functions which should make the remus specific bits easier. ~Andrew --------------060809020508080103080009 Content-Type: text/html; charset="UTF-8" Content-Length: 10279 Content-Transfer-Encoding: quoted-printable
On 03/09/14 12:53, Shriram Rajagopalan wrote:

Andrew,

On Sep 2, 2014 5:29 PM, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:
>
> On 02/09/2014 21:45, konrad.wilk@oracle.com wrote:
> > Below is a summary of the projects / features being worked on for the 4.5
> > time frame.=C2=A0 The tentative feature freeze is scheduled for September 10th,
> > which is less a week away!
> >
> > Most of the Xen patches that impacted the hypervisor and had'fair'
> > (except the HVM introspection one) I moved to the Xen 4.6 list.
> >
> > They might get Acked by maintainers in the next couple of days which would
> > be fantastic - and if so I will update the list. But perhaps not. Also
> > some are in 'good' or in 'ok' condition - but that does not mean they
> > will automatically go in Xen 4.5.
> >
> > In terms of QEMU=C2=A0 - I only had three items and since the version of QEMU
> > from upstream we are using is already established (and stable) I don't see us
> > backporting any more patches from upstream. But perhaps Stefano has some
> > other plans...
> >
> > In terms of the toolstack - I kept the ones that are in the 'fair' category
> > as I think they are easier to test/rebase/retest than the hypervisor ones.
> >
> > In terms of Linux I am keeping the 'fair' ones as by the Xen 4.6 release
> > it could be v3.19, which means there is still an upcoming merge window
> > for those.
> >
> > The "prognosis" is now the likelihood of completion in the 4.5 timeframe.
> > A bunch of items had moved to the completed phase which is fantastic.
> >
> > none - nothing yet
> > fair - still working on it, patches are prototypes or RFC
> > ok=C2=A0 =C2=A0- patches posted, acting on review
> > good - some last minute pieces
> > done - all done, might have bugs
> >
> > 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.=C2=A0 (It's OK if there are still bugs to be
> > worked out.)=C2=A0 For items in Linux, it would mean having items on track
> > to make it into the kernel released just after the scheduled 4.5 time frame.
> >
> > In terms of libvirt it has monthly releases. As such not going to track
> > every release - but closer to when RCs are out.
> >
> > =3D Timeline =3D
> >
> > We are planning on a 9-month release cycle.=C2=A0 Based on that, below are
> > our estimated dates:
> >
> > * Coding time: <=3D=3D=3D NOW, one week left!
> >
> > * 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.=C2=A0 The feature freeze may be
> > slipped for especially important features which are near completion.
> >
> > If you think your patchset MUST go in Xen 4.5 I will post the procedure
> > for requesting an exception to get them in past the feature freeze next
> > week.
> >
> > =3D Prognosis =3D
> >
> > The states are: none -> fair -> ok -> good -> done
> >
> > none - nothing yet
> > fair - still working on it, patches are prototypes or RFC
> > ok=C2=A0 =C2=A0- patches posted, acting on review
> > good - some last minute pieces
> > done - all done, might have bugs
> >
> >
> > =3D Open =3D
> >
> > =3D=3D ARM =3D=3D
> >
> > *=C2=A0 ARM - Device assigment on ARM (good)
> >=C2=A0 =C2=A0 Linux parts at risk.
> >=C2=A0 =C2=A0 v2 for hypervisor out
> >=C2=A0 =C2=A0-=C2=A0 Julien Grall
> >
> > *=C2=A0 ARM XEN_DOMCTL_memory_mapping hypercall for ARM (good)
> >=C2=A0 =C2=A0 v12 posted.
> >=C2=A0 =C2=A0-=C2=A0 Arianna Avanzini
> >
> > *=C2=A0 ARM Xen UEFI booting on ARM (ok)
> >=C2=A0 =C2=A0 v2
> >=C2=A0 =C2=A0-=C2=A0 Roy Franz
> >
> > *=C2=A0 ARM PSCI v0.2 (good)
> >=C2=A0 =C2=A0 v11 posted
> >=C2=A0 =C2=A0-=C2=A0 Parth Dixit
> >
> > *=C2=A0 ARM GICv3 support (ok)
> >=C2=A0 =C2=A0 v6a patchset (refactor in, also known as v9a); v7 posted
> >=C2=A0 =C2=A0 v9a posted which does GIC and VGIC code refactoring
> >=C2=A0 =C2=A0 v8 posted
> >=C2=A0 =C2=A0-=C2=A0 Vijay Kilari
> >
> > *=C2=A0 ARM - MiniOS (ok)
> >=C2=A0 =C2=A0 v7 posted
> >=C2=A0 =C2=A0-=C2=A0 Thomas Leonard
> >
> > *=C2=A0 ARM - VGIC emulation (ok)
> >=C2=A0 =C2=A0 Reposted as gic and vgic fixes and improvements
> >=C2=A0 =C2=A0 v12
> >=C2=A0 =C2=A0-=C2=A0 Stefano Stabellini
> >
> > *=C2=A0 ARM - XENFEAT_grant_map_11 (aka map grants refs at pfn =3D mfn) (ok)
> >=C2=A0 =C2=A0 Provide kernels an grant->MFN lookup
> >=C2=A0 =C2=A0 v4
> >=C2=A0 =C2=A0-=C2=A0 Stefano Stabellini
> >
> > *=C2=A0 ARM - Add Odroid-XU (Exynos5410) support (ok)
> >=C2=A0 =C2=A0 v4
> >=C2=A0 =C2=A0-=C2=A0 Suriyan Ramasami
> >
> > *=C2=A0 ARM implement mem_access (ok)
> >=C2=A0 =C2=A0 v3
> >=C2=A0 =C2=A0 https://github.com/tklengyel/xen/tree/arm_memaccess3
> >=C2=A0 =C2=A0-=C2=A0 Tamas K Lengyel
> >
> > =3D=3D x86 =3D=3D
> >
> > *=C2=A0 New Migration (v2). (good)
> >=C2=A0 =C2=A0 v6 posted, going on the 'good' side!
> >=C2=A0 =C2=A0-=C2=A0 Andrew Cooper & David Vrabel
>
> Work on the {lib,}xl side of things are making progress.
>
> Given the lack of stream versioning, *even* at the libxl level, both
> sets of changes need to go in together, so there is no chance of
> deferring the libxl work.
>
> PV is working and HVM is getting there.=C2=A0 Currently have a lot of
> compatibility hacks until Wei's domain json series gets accepted (or
> cherrypicked into my queue).=C2=A0 Also, making the restore side asynchronous
> is proving very difficult.
>
> Will also require some careful integration with remus.=C2=A0 I believe my
> libxc series now contains all the remus-specific bugfixes discovered,
> but I have yet to have feedback.
>

Sorry about this. Can you point me to the specific patches that you need feedback on=3F

Shriram


http://xenbits.xen.org/gitweb/=3Fp=3Dpeople/andrewcoop/xen.git;a=3Dshortlog;h=3Drefs/heads/saverestore2-v6.2

should contain all the underlying bugfixes identified from the remus libxc patch series.=C2=A0 It also contains a few new functions which should make the remus specific bits easier.

~Andrew
--------------060809020508080103080009-- --===============8021963462783568287== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============8021963462783568287==--