From: Wei Huang <w1.huang@samsung.com>
To: konrad.wilk@oracle.com, andrew.cooper3@citrix.com,
andrew.bennieston@citrix.com, avanzini.arianna@gmail.com,
ufimtseva@gmail.com, boris.ostrovsky@oracle.com,
bob.liu@oracle.com, msw@amazon.com, dslutz@verizon.com,
david.vrabel@citrix.com, daniel.kiper@oracle.com,
roger.pau@citrix.com, Kelly.Zytaruk@amd.com,
tiejun.chen@intel.com, mukesh.rathor@oracle.com,
Wei.Liu2@citrix.com, stefano.stabellini@eu.citrix.com,
julien.grall@linaro.org, malcolm.crossley@citrix.com,
zoltan.kiss@citrix.com, feng.wu@intel.com,
Paul.Durrant@citrix.com, JBeulich@suse.com, olaf@aepfle.de,
xen-devel@lists.xenproject.org
Subject: Re: Xen 4.5 development update
Date: Tue, 27 May 2014 14:18:41 -0500 [thread overview]
Message-ID: <5384E511.1000901@samsung.com> (raw)
In-Reply-To: <20140527180640.6053D1BF275@phenom.dumpdata.com>
Hi Konrad,
I would expect the following item to be added for Xen 4.5. The patch set
has been reviewed for several rounds and shouldn't have any major
technical challenge.
* Wei Huang Prognosis: 90 %
ARM VM save/restore/live migration
Also, I don't see many ARM features, other than IOMMU and memory_map
hypercall, in your list. There should be more. Maybe Stefano/IanC/Julien
can gather a list for ARM?
Thanks,
-Wei
On 05/27/2014 01:06 PM, 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 divert
> 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 frame.
> 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 frame.
> Not sure what that means for libvirt. :-)
>
> = Timeline =
>
> 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.
>
> = Prognosis =
>
> The prognosis is a numerical value of the likehood of the feature/code
> making it in the code-base.
>
> If folks prefer the fair, good, excellent marker I can switch over to
> that.
>
> = Open =
>
> * Andrew Cooper Prognosis: 100 %
> libx{c,l} error handling cleanup
> New migration.
> cpuid leveling
>
> * Andrew Benniest Prognosis: 100 %
> Netback multiqueue
>
> * Arianna Avanzini Prognosis: 100 %
> block multiqueue
> XEN_DOMCTL_memory_mapping hypercall for ARM
>
> * Elena Ufimtseva Prognosis: 0 %
> vNUMA in Xen
> vNUMA in Linux
>
> * Boris Ostrovsky Prognosis: 100 %
> VPMU - 'perf' support in Xen
> VPMU - 'perf' support in Linux
> vAPIC in PVHVM guests
>
> * Bob Liu Prognosis: 100 %
> tmem cleanups/fixes
> 1TB slow destruction
>
> * Dario Faggioli Prognosis: 0 %
> Soft affinity for vcpus (was NUMA affinity for vcpus)
>
> * Matt Wilson Prognosis: 0 %
> HVM guest NUMA
>
> * Don Slutz Prognosis: 100 %
> Bigger PCI hole in QEMU
> Re-write of HPET
>
> * David Vrabel: Prognosis: 100 %
> New migration.
>
> * Daniel Kiper Prognosis: 100 %
> GRUB2 multiboot2
> Xen multiboot2 support
> Linux pvops of Xen EFI hypercall support
> libxl/xl - xm compatibility mode for mem-max and mem-set;
> Rearrange and cleanup installation destination directories (/var -> var/lib/xen)
>
> * George Dunlap: Prognosis: 100 %
> Default to credit2
> > cpu pinning, numa affinity and cpu reservation
>
> * Roger Pau Monn챕 Prognosis: 100 %
> Xen PVH dom0
> PVH FreeBSD dom0
>
> * Konrad Rzeszutek Wilk Prognosis: 30 %
> NUMA memory scrubbing
> Performance fixes for PCI passthrough
>
> * Kelly Zytaruk Prognosis: 100 %
> AMD Radeon PCI GPU passthrough
>
> * Chen, Tiejun Prognosis: 100 %
> Intel IGD PCI GPU passthrough
>
> * Mukesh Rathor Prognosis: 100 %
> Xen PVH dom0
> Linux PVH dom0
>
> * Wei Liu Prognosis: 100 %
> 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.
>
> * Ian Campbel Prognosis: 100 %
> OSSTest: libvirt
> OSSTest: upstream QEMU
>
> * Ian Jackson Prognosis: 100 %
> xl does not handle migrate interruption gracefully
> > If you start a localhost migrate, and press "Ctrl-C" in the middle, you get two hung domains
>
> * Stefano Stabellini Prognosis: 100 %
> <NONE>
>
> * Julien Grall Prognosis: 100 %
> ARM IOMMU support
>
> * Malcolm Crossley Prognosis: 100 %
> IOMMU ABI for guests to map their DMA regions
>
> * Zoltan Kiss Prognosis: 100 %
> Netback grant table manipulations
> "Short" grant copy (just header) of packets.
>
> * Feng Wu Prognosis: 100 %
> SMAP
> alternative_asm in Xen
>
> * Zhang, Yang Z Prognosis: 100 %
> dirty vram / IOMMU bug
>
> * Paul Durrant Prognosis: 100 %
> ioreq-server, aka secondary emulators
>
> * Jan Beulich Prognosis: 100 %
> Stability
>
> * Olaf Hering Prognosis: 100 %
> libvirt and xl discard support, so that libvirt can start using it
> pvscsi should be targeted for 4.5, a prototype exists
> live migration knobs, there is no suitable code yet, just ideas
>
> * Joe Doe aka not assigned to anybody Prognosis: 0 %
> PoD fixes
> TLB flushing without locks in Xen
> xl does not support specifying virtual function for passthrough device
> > http://bugs.xenproject.org/xen/bug/22
> PCI hole resize support hvmloader/qemu-traditional/qemu-upstream with PCI/GPU passthrough
> > http://bugs.xenproject.org/xen/bug/28
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-05-27 19:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 18:06 Xen 4.5 development update konrad.wilk
2014-05-27 19:18 ` Wei Huang [this message]
2014-05-28 11:43 ` Stefano Stabellini
2014-05-28 15:47 ` Julien Grall
2014-05-27 22:45 ` Wei Liu
2014-05-27 23:43 ` Andrew Cooper
2014-05-28 15:41 ` Konrad Rzeszutek Wilk
[not found] ` <CAGU+auv+nJAU9Ys9J15V03t-4r=ScVocomBKEN8dHwUQHTmT0w@mail.gmail.com>
2014-05-27 23:56 ` Aravindh Puthiyaparambil (aravindp)
2014-05-28 7:16 ` Jan Beulich
2014-05-28 18:49 ` Aravindh Puthiyaparambil (aravindp)
2014-05-28 15:42 ` Konrad Rzeszutek Wilk
2014-05-28 10:01 ` Roger Pau Monné
2014-05-28 15:46 ` Konrad Rzeszutek Wilk
2014-05-28 11:35 ` Stefano Stabellini
2014-05-29 1:25 ` Xu, Dongxiao
2014-05-30 10:09 ` Don Slutz
2014-05-30 13:57 ` Zytaruk, Kelly
2014-05-30 14:09 ` Don Slutz
2014-06-04 13:20 ` Lars Kurth
2014-06-04 13:50 ` Zytaruk, Kelly
2014-06-04 14:41 ` Sander Eikelenboom
-- strict thread matches above, loose matches on Subject: below --
2014-06-18 20:22 konrad.wilk
2014-06-18 20:36 ` Julien Grall
2014-06-18 20:47 ` Andrew Cooper
2014-06-19 7:56 ` Paul Durrant
2014-06-18 21:24 ` Aravindh Puthiyaparambil (aravindp)
2014-06-18 21:56 ` Roy Franz
2014-06-19 4:05 ` Vijay Kilari
2014-06-19 10:23 ` Wei Liu
2014-06-19 12:05 ` Stefano Stabellini
2014-06-19 13:24 ` Don Slutz
2014-06-19 16:37 ` Jan Beulich
2014-06-19 16:46 ` Andrew Cooper
2014-06-19 14:15 ` Boris Ostrovsky
2014-06-20 8:50 ` Dario Faggioli
2014-06-23 14:25 ` Lars Kurth
2014-06-26 14:10 ` Ian Campbell
2014-06-27 14:55 ` Konrad Rzeszutek Wilk
2014-07-01 16:43 konrad.wilk
2014-07-02 11:33 ` George Dunlap
2014-07-02 12:23 ` Jan Beulich
2014-07-11 6:51 ` Dario Faggioli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5384E511.1000901@samsung.com \
--to=w1.huang@samsung.com \
--cc=JBeulich@suse.com \
--cc=Kelly.Zytaruk@amd.com \
--cc=Paul.Durrant@citrix.com \
--cc=Wei.Liu2@citrix.com \
--cc=andrew.bennieston@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=avanzini.arianna@gmail.com \
--cc=bob.liu@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=daniel.kiper@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=dslutz@verizon.com \
--cc=feng.wu@intel.com \
--cc=julien.grall@linaro.org \
--cc=konrad.wilk@oracle.com \
--cc=malcolm.crossley@citrix.com \
--cc=msw@amazon.com \
--cc=mukesh.rathor@oracle.com \
--cc=olaf@aepfle.de \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tiejun.chen@intel.com \
--cc=ufimtseva@gmail.com \
--cc=xen-devel@lists.xenproject.org \
--cc=zoltan.kiss@citrix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).