[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen 4.5 development update (September update). Feature freeze slip by two weeks.

On Wed, Sep 10, 2014 at 1:05 PM, <konrad.wilk@xxxxxxxxxx> wrote:
The feature freeze has moved by two weeks. That means it is scheduled
to be on September 24th.

If you think you will need a feature freeze exception, read below.

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:

* Feature Freeze: 24th September 2014
* First RC: 15th 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

= 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

= Feature freeze exception =

When we get to September 24th, the code "freezing point" will commence;
which means that starting on that day non-bug fixes need a freeze exception
to be included.

Remember our goal for the release:
 1. A bug-free release
 2. An awesome release
 3. An on-time release

Accepting a new feature may make Xen more awesome; but it also
introduces a risk that it will introduce more bugs. That bug may be
found before the release (threatening #3), or it may not be found
until after the release (threatening #1). Each freeze exception
request will attempt to balance the benefits (how awesome the
exception is) vs the risks (will it cause the release to slip, or
worse, cause a bug which goes un-noticed into the final release).

The idea is that today we will be pretty permissive, but that we will
become progressively more conservative until the first RC, which is
scheduled for 3 weeks' time (October 15). After that, we will only
accept bug fixes.

Bug fixes can be checked in without a freeze exception throughout the
code freeze, unless the maintainer thinks they are particularly high
risk. In later RC's, we may even begin rejecting bug fixes if the
broken functionality is small and the risk to other functionality is

Features which are currently marked "experimental" or do not at the
moment work at all cannot be broken really; so changes to code only
used by those features should be able to get a freeze exception

Features which change or add new interfaces which will need to be
supported in a backwards-compatible way (for instance, vNUMA) will
need freeze exceptions to make sure that the interface itself has
enough time to be considered stable.

Hello Konrad

I am working on toolstack patches for vNUMA and looks like I will
need to request exception for these. Hopefully, by today I will have the patches out, but
I am sure they will need some modifications.
As we discussed, I will email to maintainers to discuss this.



These are guidelines and principles to give you an idea where we're
coming from; if you think there's a good reason why making an
exception for you will help us achieve goals 1-3 above better than not
doing so, feel free to make your case.

= Open =

== ARM ==

*Â ARM Xen UEFI booting on ARM (fair/ok)
 - Roy Franz

*Â ARM GICv3 support (ok)
 Âv10 posted
 - Vijay Kilari

*Â ARM - VGIC emulation (ok)
 ÂReposted as gic and vgic fixes and improvements
 - Stefano Stabellini

*Â ARM - Add Odroid-XU (Exynos5410) support (ok)
 - Suriyan Ramasami

*Â ARM implement mem_access (ok)
 - Tamas K Lengyel

== x86 ==

*Â xc_reserved_device_memory_map in hvmloader to avoid conflicting MMIO/RAM (good)
 - Tiejun Chen

*Â New Migration (v2). (good)
 Âv6 posted, going on the 'good' side!
 - Andrew Cooper & David Vrabel

*Â PVH - AMD hardware support. (fair)
 - Mukesh Rathor

*Â VMware backdoor (hypercall) (ok)
 Âv2 posted.
 - Don Slutz

*Â VPMU - 'perf' support in Xen (good)
 Âv10 posted
 ÂNeed perf aware person to review for final ack.
 - Boris Ostrovsky

*Â Cache QoS Monitoring - hypercalls (ok)
 ÂJust hypercalls - no toolstack changes.
 ÂHit a snag with rdmsr/IPI/wrmsr/IPI, possible redesign
 - Chao Peng, Dongxiao Xu, and Shantong Kang

*Â XenRT (Preemptive Global Earliest Deadline First) (good)
 - Meng Xu

*Â Introspection of HVM guests (ok)
 - Razvan Cojocaru

*Â Xen Boot Information (xbi) (fair)
 ÂDependency for GRUB2 + EFI work
 ÂSee http://lists.xen.org/archives/html/xen-devel/2013-05/msg02281.html
 - Daniel Kiper

== lib{xc,xl} and toolstack ==

*Â vNUMA in Xen toolstack (ok)
 Âv11 posted
 ÂHypervisor part in
 - Elena Ufimtseva

*Â Remus in Xen (libxl) (good)
 Âurl: https://github.com/macrosheep/xen/tree/remus-v19
 - Gui Jianfeng
 - Yang Hongyang
 - Dong, Eddie

== Linux ==

*Â Linux block multiqueue (fair)
 - Arianna Avanzini

*Â Netback grant table manipulations (ok)
 - Zoltan Kiss

*Â VPMU - 'perf' support in Linux (ok)
 ÂDepends on Xen patches
 - Boris Ostrovsky

*Â vNUMA in Linux (ok)
 Âv6 posted
 - Elena Ufimtseva

*Â vsyscall in Linux (fair)
 - Konrad Rzeszutek Wilk

*Â COLO Agent in Linux (fair)
 - Gui Jianfeng
 - Yang Hongyang
 - Dong, Eddie

*Â vAPIC in PVHVM guests (Linux side) (none)
 - Boris Ostrovsky

*Â ARM - Device assigment usage in Linux code (arch/arm) (none)
 - Julien Grall

*Â Fix PAT in Linux kernel (aka Full support for PAT) (ok)
 - Juergen Gross

*Â Linux ARM - Device assigment (fair)
 - Julien Grall

== FreeBSD ==

*Â PVH FreeBSD dom0 (ok)
 ÂFreeBSD 11 goal. Toolstack side done in Xen 4.5
 - Roger Pau MonnÃ

== Other OSes (MiniOS, QNX) ==

*Â PV drivers for automotive kernels (fair)
 - Artem Mygaiev

*Â mini-os: xenbus changes for rump kernels (ok)
 Âbranch: base.dev-xen-xenbus.v1..dev-xen-xenbus.v1
 Âv2 posted
 - Ian Jackson

== GRUB2 ==

*Â GRUB2 multiboot2 (fair)
 - Daniel Kiper


*Â OSSTest: libvirt (good)
 - Ian Campbell

== Deferred to QEMU v2.next ==

*Â Using qemu-upstream in a stubdomain (fair)
 ÂWill use rump kernels.
 - Ian Jackson

*Â AMD Radeon PCI GPU passthrough (none)
 ÂFocusing on Xen 4.2 and qemu-traditional
 - Kelly Zytaruk

*Â Intel IGD PCI GPU passthrough (ok)
 Âv5 posted
 - Chen, Tiejun

*Â Xen PV block driver in OVMF (UEFI in guest) (ok)
 - Anthony PERARD

== Deferred to Xen hypervisor 4.6 ==

*Â extending mem_access support to PV domain (fair)
 ÂRFC v2
 - Aravindh Puthiyaparambil (aravindp)

*Â Repurpose SEDF Scheduler for Real-time (fair)
 ÂRFC patch posted (v2)
 - Joshua Whitehead, Robert VanVossen

*Â ARM remote processor iommu module (GPUs + IPUs) (fair)
 Âv3 posted
 - Andrii Tseglytskyi

*Â dirty vram / IOMMU bug (fair)
 - Zhang, Yang Z

*Â Xen multiboot2-EFI support (fair)
 ÂNeeded for GrUB2
 ÂDepends on Xen Boot info (rework multiboot and other structs)
 ÂSee http://lists.xen.org/archives/html/xen-devel/2013-05/msg02281.html
 ÂRFC posted
 - Daniel Kiper

*Â Support controlling the max C-state sub-state (ok)
 Âv3 posted
 - Ross Lagerwall

*Â IOMMU ABI for guests to map their DMA regions (fair)
 - Malcolm Crossley

*Â Default to credit2 (none)
 Âcpu pinning, numa affinity and cpu reservation
 - George Dunlap

*Â Convert tasklet to per-cpu tasklets (fair)
 ÂRFC posted
 - Konrad Rzeszutek Wilk

*Â Further tmem cleanups/fixes (16TB etc) (fair)
 - Bob Liu

*Â 1TB slow destruction (ok)
 - Bob Liu

*Â ARM VM save/restore/live migration (none)
 ÂNeed to rebased against migrationv2 - no code posted.
 - Junghyun Yoo

*Â ARM GICv2m support (none)
 - Linaro (unknown)

== Deferred to Xen toolstack 4.6 ==

*Â pvscsi in libxl (fair)
 - Juergen Gross and Olaf

*Â COarse-grain LOck-stepping Virtual Machines in Xen (fair)
 ÂRFC v3 posted, based on remus-v19
 - Wen Congyang
 - Gui Jianfeng
 - Yang Hongyang
 - Dong, Eddie

*Â extend the xenstore ring with a 'closing' signal (fair)
 ÂRFC patch posted
 - David Scott

*Â libxl migrationv2 patches. (none)
 - Andrew Cooper & David Vrabel

*Â tmem migrationv2 patches. (none)
 - Bob Liu & Andrew Cooper & David Vrabel

*Â Remus using migration-v2 (fair)
 ÂRFC posted - depends on v6 of 'New Migration'
 - Yang Hongyang

*Â snapshot API extension (checkpointing disk) (ok)
 ÂHis email bounces.
 - Bamvor Jian Zhang

*Â Rearrange and cleanup installation destination directories (/var -> var/lib/xen) (fair)
 - Daniel Kiper

*Â libxl/xl - xm compatibility mode for mem-max and mem-set; (ok)
 - Daniel Kiper

*Â xl list --long (and some related xl commands) have some bugs (none)
 - Zhigang Wang

*Â Xen HPET interrupt fixes (fair)
 Âbehind migration v2
 - Andrew Cooper

*Â cpuid leveling (none)
 - Andrew Cooper

*Â live migration knobs, there is no suitable code yet, just ideas (none)
 - Olaf Hering

*Â xl does not handle migrate interruption gracefully (none)
 ÂIf you start a localhost migrate, and press "Ctrl-C" in the middle, you get two hung domains
 - Ian Jackson

*Â IO-NUMA - hwloc and xl (none)
 ÂAndrew Cooper had an RFC patch for hwloc
 Âadd restrictions as to which devices cannot safely/functionally be split apart.
 - Boris Ostrovsky

*Â HVM guest NUMA (none)
 - Matt Wilson

*Â PVH - Migration of PVH DomUs. (none)
 ÂDepends on migration2 code
 - Roger Pau MonnÃ

*Â PVH - Migration of guests from a PVH dom0Â (none)
 ÂDepends on migration2 code
 - Roger Pau MonnÃ

*Â "Short" grant copy (just header) of packets. (none)
 - Zoltan Kiss

== Up for grabs ==

*Â OSSTest - also test Linux PVH guests

*Â PoD fixes
 Âif you boot with memory <= maxmem we have a size estimation bug

*Â TLB flushing without locks in Xen

*Â xl does not support specifying virtual function for passthrough device

*Â PCI hole resize support hvmloader/qemu-traditional/qemu-upstream with PCI/GPU passthrough

*Â libx{c,l} error handling cleanup

*Â Adding missing 'xend' features in libxl

*Â xl list -l on a dom0-only system

*Â xl list -l doesn't contain tty console port

*Â xl: passing more defaults in configuration in xl.conf
 ÂThere are a number of options for which it might be useful to pass a default in xl.conf. For example, if we could have a default "backend" parameter for vifs, then it would be easy to switch back and forth between a backend in a driver domain and a backend in dom0.

*Â PVH - PVH working with shadow.
 ÂBased on Tim's work

*Â PVH - PCI passthrough for DomU.

*Â AMD performance regressions

*Â Performance due to hypercall preemption. More preemptions - slower. (none)

== Completed ==

*Â ARM - MiniOS (done)
 Âv7 posted
 - Thomas Leonard

*Â ARM XEN_DOMCTL_memory_mapping hypercall for ARM (done)
 Âv12 posted.
 - Arianna Avanzini

*Â libxl work - JSON to keep track of guest configs (done)
 - Wei Liu

*Â ARM - XENFEAT_grant_map_11 (aka map grants refs at pfn = mfn) (done)
 ÂProvide kernels an grant->MFN lookup
 - Stefano Stabellini

*Â ARM PSCI v0.2 (done)
 Âv11 posted
 - Parth Dixit

*Â pvSCSI in Linux (fronted and backend) (done)
 - Juergen Gross

*Â alternative_asm in Xen (done)
 - Feng Wu

*Â SMAP (done)
 - Feng Wu

*Â Re-write of vHPET (done)
 Âaka hvm/hpet: Detect comparator values in the past
 - Don Slutz

*Â vAPIC in PVHVM guests (Xen side) (done)
 - Boris Ostrovsky

*Â libvirt and xl discard support, so that libvirt can start using it (done)
 - Olaf Hering

*Â Xen PVH dom0 (done)
 - Mukesh Rathor

*Â Linux PVH dom0 (done)
 - Mukesh Rathor

*Â OSSTest: upstream QEMU (done)
 - Ian Campbell

*Â amd_ucode cleanups, verify patch size(enhancement) (mostly in master except one patch)

*Â Data breakpoint Extension support (new-feat) (in master)

*Â Feature masking MSR support (enhancement) (in master)

*Â Support BRCM TruManage chip (Serial over LAN support) (new-feat) (in master)

*Â fix vmce_amd* functions, unify mce_amd mcheck initialization (fixes/cleanups)

*Â multiple AMD container files appended together in initrd (early initramfs)
 - Aravind and Suravee

*Â NUMA memory scrubbing (done)
 - Konrad Rzeszutek Wilk

*Â ARMÂ - IOMMU support (done)
 - Julien Grall

*Â ioreq-server, aka secondary emulators (done)
 - Paul Durrant

*Â Netback multiqueue (good)
 - Wei Liu

*Â ARM Interrupt latency reduction (no maintenance interrupts) (good)
 - Stefano Stabellini

*Â Bigger PCI hole in QEMU (done)
 ÂNeeds to be rebased
 - Don Slutz

*Â ARM DRA7 support (done)
 Âv3 posted
 Âv3 with comments applied
 - Andrii Tseglytskyi

*Â rework VM Generation ID (done)
 Âv7 posted
 - David Vrabel

*Â Soft affinity for vcpus (was NUMA affinity for vcpus) (good)
 Âv11 posted
 - Dario Faggioli

*Â Linux pvops of Xen EFI hypercall support (done)
 - Daniel Kiper

*Â ARM: Use super pages in p2m (done)
 Âv5 posted
 - Ian Campbell

*Â QEMU 2.0 branch for qemu-upstream (done)
 ÂIt is v2.0 with 2.1 Xen backports.
 - Stefano Stabellini

*Â systemd support (done)
 - Luis R. Rodriguez

*Â Soft affinity for vcpus libxl/xl changes (done)
 Âv13 posted
 - Dario Faggioli

*Â HT enabled, virtualization overhead is high (Xen 4.4) (done)
 Âkernbench demonstrated it
 ÂLooking and tracing
 ÂFalse alarm.
 - Dario Faggioli

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.