From: Julien Grall <julien.grall@arm.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>, Wei Liu <wei.liu2@citrix.com>
Cc: Zibby Keaton <zkeaton@linuxfoundation.org>,
Xen-devel <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: Xen 4.7 Headline Features (for PR)
Date: Fri, 22 Apr 2016 18:30:25 +0100 [thread overview]
Message-ID: <571A5FB1.1020204@arm.com> (raw)
In-Reply-To: <000436D9-F475-44EA-9487-F6694B831080@gmail.com>
Hi Lars,
On 22/04/16 15:19, Lars Kurth wrote:
>
>> On 22 Apr 2016, at 14:39, Wei Liu <wei.liu2@citrix.com> wrote:
>>
>> On Fri, Apr 22, 2016 at 02:26:39PM +0100, Lars Kurth wrote:
>>> Folks,
>>>
>>> given that we have we are getting close to RC's, I would like to start to spec out the headline Features for the press release. The big items I am aware of are COLO. I am a little confused about xSplice.
>>>
>>> Maybe we can use this thread to start collating a short-list.
>>>
>
> Typically we have 3-5 Headline Features in a press release.
>
>> xSplice is definitively the first one on my list. I'm actually holding
>> off cutting RC1 waiting for it to be merged.
>
> This would definitely be the #1 Headline feature then. It's the single most important thing we have done in a while and it has the potential to positive
>
>> COLO is also a candidate, but there are many components that are not yet
>> upstream. Those are not necessarily part of xen.
>
> Alright, we may need to be careful as to not raise wrong expectations, if there are missing pieces say in QEMU. On the other hand, having this in place before KVM is also nice.
>
>> ACPI support on ARM is also a possible candidate.
Note that this feature is considered as a tech preview and not enabled
by default in Xen (you need to add XEN_CONFIG_EXPERT=y on the command line).
Other headline features:
* Wallclock support
* Support of PSCI 1.0 for the host
* Drop the support for HIP04 platform
> Agreed. Also easy to explain.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-22 17:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 13:26 Xen 4.7 Headline Features (for PR) Lars Kurth
2016-04-22 13:39 ` Wei Liu
2016-04-22 13:59 ` Wei Liu
2016-04-22 14:19 ` Lars Kurth
2016-04-22 14:23 ` George Dunlap
2016-04-22 17:30 ` Julien Grall [this message]
2016-04-22 13:48 ` Juergen Gross
2016-04-22 14:08 ` George Dunlap
2016-04-22 14:22 ` Lars Kurth
2016-04-22 14:25 ` George Dunlap
2016-04-24 1:06 ` Doug Goldstein
2016-04-27 13:12 ` Lars Kurth
2016-05-02 4:28 ` Doug Goldstein
2016-04-22 14:29 ` Wei Liu
2016-04-22 14:24 ` Vitaly Kuznetsov
2016-04-22 14:12 ` Meng Xu
2016-04-22 14:29 ` Andrew Cooper
2016-04-22 14:43 ` Lars Kurth
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=571A5FB1.1020204@arm.com \
--to=julien.grall@arm.com \
--cc=lars.kurth.xen@gmail.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=zkeaton@linuxfoundation.org \
/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).