Re: [Xen-devel] Xen 4.5 development update (July update)

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 03/09/14 12:53, Shriram Rajagopalan wrote:

Andrew,

On Sep 2, 2014 5:29 PM, "Andrew Cooper" <andrew.cooper3@xxxxxxxxxx> wrote:
>
> On 02/09/2014 21:45, konrad.wilk@xxxxxxxxxx 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

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