From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Wei Liu <wei.liu2@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Cc: jgross@suse.com, Lars Kurth <lars.kurth@xenproject.org>,
xiecl.fnst@cn.fujitsu.com, Jan Beulich <JBeulich@suse.com>,
wency@cn.fujitsu.com, jonathan.davies@citrix.com,
George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
zhaoshenglong@huawei.com, Ian Jackson <Ian.Jackson@eu.citrix.com>,
xumengpanda@gmail.com, Julien Grall <julien.grall@arm.com>,
yu.c.zhang@linux.intel.com, quan.xu@intel.com, dave@recoil.org,
lichong659@gmail.com
Subject: Re: List of projects for 4.7
Date: Fri, 18 Mar 2016 17:18:11 +0100 [thread overview]
Message-ID: <56EC2A43.6080909@m2r.biz> (raw)
In-Reply-To: <20160318120725.GA9257@citrix.com>
Il 18/03/2016 13:07, Wei Liu ha scritto:
> Hi all
>
> Today is that last posting day for new features. And we are two weeks
> away from the anticipated freeze date.
>
> I've gone through the outstanding patch series on the list and ask for
> input from various core community members. I've enumerated a list
> here, which covers several areas of this release and can be used as a
> guideline.
>
> Important and close patch, new features:
> 1. xSplice
> 2. CPUID levelling
> 3. ARM ACPI
> 4. COLO HA
> 5. RTDS per-vcpu parameter setting
> 6. Event driven RTDS
Hi, what about "Domain snapshot API"? From a fast search I not found
recent news about it.
Thanks for any reply and sorry for my bad english.
>
> Important bug fixes:
> 1. Intel VT-d flush issue
> 2. SMEP / SMAP fix
> 3. QEMU hotplug script fix
>
> Note, it is possible for bug fixes to go in after freeze.
>
> Nice to have, not very complicated patch sets:
> 1. IOREQ server P2M type
> 2. QEMU-based PVUSB backend
> 3. Oxenstored improvement
> 4. Load bios via toolstack
>
> I think it would be good to use the remaining time to focus on things
> that are close, important or both.
>
> Thanks
> Wei.
>
> _______________________________________________
> 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:[~2016-03-18 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 12:07 List of projects for 4.7 Wei Liu
2016-03-18 13:44 ` Jan Beulich
2016-03-18 15:05 ` Meng Xu
2016-03-18 15:34 ` Wei Liu
2016-03-18 16:18 ` Fabio Fantoni [this message]
2016-03-18 16:22 ` Wei Liu
2016-03-18 16:23 ` Chong Li
2016-03-19 5:45 ` Shannon Zhao
2016-03-21 11:51 ` Julien Grall
2016-03-19 8:10 ` Olaf Hering
2016-03-19 20:21 ` Wei Liu
2016-03-21 10:03 ` Olaf Hering
2016-03-21 5:21 ` Juergen Gross
2016-03-21 14:57 ` Wei Liu
2016-03-21 10:11 ` Paul Durrant
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=56EC2A43.6080909@m2r.biz \
--to=fabio.fantoni@m2r.biz \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=dave@recoil.org \
--cc=george.dunlap@eu.citrix.com \
--cc=jgross@suse.com \
--cc=jonathan.davies@citrix.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth@xenproject.org \
--cc=lichong659@gmail.com \
--cc=quan.xu@intel.com \
--cc=wei.liu2@citrix.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xenproject.org \
--cc=xiecl.fnst@cn.fujitsu.com \
--cc=xumengpanda@gmail.com \
--cc=yu.c.zhang@linux.intel.com \
--cc=zhaoshenglong@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.