From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, Oleksandr_Andrushchenko@epam.com
Subject: Re: Xen 4.9 Development Update
Date: Fri, 9 Dec 2016 14:57:04 +0200 [thread overview]
Message-ID: <6bd22e80-afc3-aa69-9714-e158d702bbd1@gmail.com> (raw)
In-Reply-To: <69f17abe-9c75-0182-c9a5-38673cc331d8@arm.com>
Hi, all!
On 12/09/2016 12:18 PM, Julien Grall wrote:
> Hi Stefano,
>
> On 08/12/16 22:00, Stefano Stabellini wrote:
>> On Thu, 8 Dec 2016, Julien Grall wrote:
>>> This email only tracks big items for xen.git tree. Please reply for
>>> items you
>>> woulk like to see in 4.9 so that people have an idea what is going
>>> on and
>>> prioritise accordingly.
>>>
>>> You're welcome to provide description and use cases of the feature
>>> you're
>>> working on.
>>>
>>> = Timeline =
>>>
>>> We now adopt a fixed cut-off date scheme. We will release twice a
>>> year. The upcoming 4.9 timeline are as followed:
>>>
>>> * Last posting date: March 17th, 2017
>>> * Hard code freeze: March 31th, 2017
>>> * RC1: TBD
>>> * Release: June 2, 2017
>>>
>>> Note that we don't have freeze exception scheme anymore. All patches
>>> that wish to go into 4.9 must be posted no later than the last posting
>>> date. All patches posted after that date will be automatically queued
>>> into next release.
>>>
>>> RCs will be arranged immediately after freeze.
>>>
>>> = Projects =
>>>
>>> == Hypervisor ==
>>>
>>> * Boot Xen on EFI platforms using GRUB2 (multiboot2 protocol)
>>> - Daniel Kiper
>>>
>>> * Per-cpu tasklet
>>> - Konrad Rzeszutek Wilk
>>>
>>> === x86 ===
>>>
>>> * Allow ioreq server interface to support XenGT
>>> - Yu Zhang
>>> - Paul Durrant
>>>
>>> * PVHv2 support
>>> - Roger Pau Monne
>>>
>>> * vNVDIMM support
>>> - Haozhong Zhang
>>>
>>> === ARM ===
>>>
>>> * ITS emulation (Dom0 only)
>>> - Andre Przywara
>>>
>>> * Altp2m for ARM
>>> - Sergej Proskurin
>>>
>>> * Support Tegra SoCs
>>> - Kyle Temkin
>>>
>>> == Toolstack ==
>>>
>>> * Libxl PVSCSI support
>>> - Olaf Hering
>>>
>>> * Libxl depriv QEMU
>>> - Ian Jackson
>>>
>>> * Logging solution for Xen system
>>> - Wei Liu
>>>
>>> * Remove blktap2
>>> - Wei Liu
>>>
>>> == Mini-OS ==
>>>
>>> == GRUB ==
>>>
>>> * Support booting Xen ARM
>>> - Fu Wei
>>>
>>
>> Should we have a section on new PV drivers? If so, I suggest to add:
>> - Xen transport for 9pfs
>> - PV Calls
>
> Good idea. We could also include DRM and PV Sound (CC Oleksandr).
>
This is a great idea. Let me explain what we have and what the direction is:
1. Frontends which we already have, working, but need to refactor/cleanup:
1.1. PV sound
1.2. PV DRM
1.3. DISPL protocol, I will push v1 for review right after sndif done
1.3. PV DRM mapper (Dom0 generic DRM driver to implement DRM zero copy
via DRM Prime buffer sharing)
1.4. PV events not done, but we are considering [1]. If it fits and is
maintained,
then we'll probably stick to it, otherwise new PV will be created
2. Backends, for the above frontends already implemented:
2.1. A unified library for Xen backends (libxenbe)
2.2. DRM + Wayland
2.3. ALSA
2.4. Events not implemented yet
All the above sources are available on *public* Github repos
(I can provide links on request) and the intention is to
upstream.
3. We are interested in extending xl + libxl to support new PV drivers
Thank you,
Oleksandr
[1] https://github.com/xenbedded/openxt_kbdfront
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-09 12:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 15:12 Xen 4.9 Development Update Julien Grall
2016-12-08 22:00 ` Stefano Stabellini
2016-12-09 10:18 ` Julien Grall
2016-12-09 12:57 ` Oleksandr Andrushchenko [this message]
2016-12-09 13:57 ` Pasi Kärkkäinen
2016-12-09 14:10 ` Oleksandr Andrushchenko
2016-12-09 19:01 ` Stefano Stabellini
2016-12-09 19:09 ` Andrew Cooper
2017-01-26 12:27 ` Julien Grall
2017-01-26 17:06 ` Wei Liu
2017-01-30 15:32 ` Julien Grall
2017-01-30 15:45 ` Wei Liu
2017-02-08 17:53 ` Julien Grall
2016-12-14 13:45 ` Artem Mygaiev
[not found] <E1cF0Mx-0005da-Th@lists.xenproject.org>
2016-12-08 15:20 ` Jan Beulich
2016-12-08 15:36 ` Wei Liu
2016-12-08 15:57 ` Jan Beulich
2016-12-08 16:00 ` Wei Liu
-- strict thread matches above, loose matches on Subject: below --
2017-01-30 15:33 Julien Grall
[not found] <4c6084d167e041db9bc35dabe1e68c15@LASPEX02CAS01.citrite.net>
2017-01-30 16:21 ` Wei Liu
[not found] <E1cYDxP-0001LM-H5@lists.xenproject.org>
2017-01-31 13:51 ` Oleksandr Andrushchenko
2017-02-08 18:03 ` Julien Grall
2017-02-08 18:17 ` Konrad Rzeszutek Wilk
2017-02-08 18:56 ` Oleksandr Andrushchenko
2017-02-08 19:29 ` Julien Grall
2017-02-08 19:42 ` Oleksandr Andrushchenko
2017-02-08 19:27 ` Julien Grall
2017-02-08 18:59 ` Tamas K Lengyel
2017-02-15 21:40 ` Sergej Proskurin
2017-02-20 7:22 ` Haozhong Zhang
2017-03-28 14:20 Julien Grall
[not found] <E1csryw-0002dr-7q@lists.xenproject.org>
2017-03-30 18:24 ` Oleksandr Tyshchenko
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=6bd22e80-afc3-aa69-9714-e158d702bbd1@gmail.com \
--to=andr2000@gmail.com \
--cc=Oleksandr_Andrushchenko@epam.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).