Mailing List Archive

Xen 4.12 Development Update
This email only tracks big items for xen.git tree. Please reply for items you
would like to see in 4.12 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 about every 8 months.
The upcoming 4.12 timeline are as followed:

* Last posting date: December 14th, 2018
[. as this is just before Christmas some maintainers might ask for an
earlier last posting date if their Ack is needed. ]
* Hard code freeze: January 11th, 2019
* RC1: TBD
* Release: March 7th, 2019

Note that we don't have freeze exception scheme anymore. All patches
that wish to go into 4.12 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.

We recently introduced a jira instance to track all the tasks (not only big)
for the project. See: https://xenproject.atlassian.net/projects/XEN/issues.

Most of the tasks tracked by this e-mail also have a corresponding jira task
referred by XEN-N.

I have started to include the version number of series associated to each
feature. Can each owner send an update on the version number if the series
was posted upstream?

= Projects =

== Hypervisor ==

* Per-cpu tasklet
- XEN-28
- Konrad Rzeszutek Wilk

=== x86 ===

* guest resource mapping (v18)
- Paul Durrant

* vNVDIMM support for HVM guest (RFC v4)
- XEN-45
- Haozhong Zhang

* hypervisor x86 instruction emulator additions (v4)
- Jan Beulich

* PV-IOMMU
- Paul Durrant

* HVM guest CPU topology support (RFC)
- Chao Gao

* Intel Processor Trace virtualization enabling (v1)
- Luwei Kang

=== ARM ===

* SMMUv3 driver (RFC v4)
- Sameer Goel

* IORT support (RFC)
- Manish Jaggi

== Grub2 ==

* Support PVH guest boot (v1)
- Juergen Gross

== Completed ==


Juergen Gross

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: Xen 4.12 Development Update [ In reply to ]
> On Jul 27, 2018, at 12:19, Juergen Gross <jgross@suse.com> wrote:
>
> This email only tracks big items for xen.git tree. Please reply for items you
> would like to see in 4.12 so that people have an idea what is going on and
> prioritise accordingly.

Two additional items:

1. Linux stub domains, series posted by the Qubes team. A variant of this approach has been used by OpenXT for several years.
https://lists.xen.org/archives/html/xen-devel/2018-07/msg02616.html

2. "Argo" inter-VM communication mechanism, discussed at Xen Summit 2018 design session, design doc forthcoming. Variants of this technology have been used in OpenXT and uXen/Bromium for several years.

> We recently introduced a jira instance to track all the tasks (not only big)
> for the project. See: https://xenproject.atlassian.net/projects/XEN/issues.
>
> Most of the tasks tracked by this e-mail also have a corresponding jira task
> referred by XEN-N.

Could we start using the "Affects Version" and "Fix Version" of JIRA, with values for currently supported releases, plus the next two releases (4.12 and 4.13)? This will enable the use of filters and issue tracking for prior releases.

I can create JIRA tickets for the two tasks listed above, if there are no objections.

Rich
Re: Xen 4.12 Development Update [ In reply to ]
On 12/09/18 10:20, Jan Beulich wrote:
>>>> On 12.09.18 at 08:54, <jgross@suse.com> wrote:
>> === x86 ===
>>
>> * guest resource mapping (v18)
>> - Paul Durrant
>
> That's all gone in by now? Paul?
>
>> * hypervisor x86 instruction emulator additions (v4)
>> - Jan Beulich
>
> Where's this "v4" coming from? The presently relevant series is
> at v2 right now, with (much bigger) v3 around the corner.

That is the carry-over from 4.11, where the related series was at v4.
You asked me to keep it for 4.12.


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: Xen 4.12 Development Update [ In reply to ]
>>> On 12.09.18 at 10:30, <jgross@suse.com> wrote:
> On 12/09/18 10:20, Jan Beulich wrote:
>>>>> On 12.09.18 at 08:54, <jgross@suse.com> wrote:
>>> === x86 ===
>>>
>>> * guest resource mapping (v18)
>>> - Paul Durrant
>>
>> That's all gone in by now? Paul?
>>
>>> * hypervisor x86 instruction emulator additions (v4)
>>> - Jan Beulich
>>
>> Where's this "v4" coming from? The presently relevant series is
>> at v2 right now, with (much bigger) v3 around the corner.
>
> That is the carry-over from 4.11, where the related series was at v4.
> You asked me to keep it for 4.12.

The item needs to be kept, because we're still far away from its
completion. I think there's going to be more than just AVX512
work until we can consider the emulator sufficiently complete - at
the very least support for {F,FX,X}{SAVE,RSTOR} is going to be
wanted, which obviously is going to be yet another series. And
who knows what new ISA extensions the vendors come up with
by the time we get there.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: Xen 4.12 Development Update [ In reply to ]
On 29/11/2018 21:16, Volodymyr Babchuk wrote:
> Hello Jurgen,
>
> I just want to clarify
>
>> !!! Last posting date for patches touching ARM code is only 2 days away !!!
>
>> * TEE mediator (and OP-TEE) support in XEN (v2)
>> - Volodymyr Babchuk
> I'm currently working on v3 of this series. But looks like I will not
> be able to finish v3 before 1 Dec. Is this okay?

The "last posting day" refers to the initial submission of a patch
(series). So having sent V1 before is enough for that. You still have
to reach agreement with the maintainers before freeze date, of course.


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: Xen 4.12 Development Update [ In reply to ]
On Mon, Dec 17, 2018 at 7:41 AM Razvan Cojocaru
<rcojocaru@bitdefender.com> wrote:
>
> Hello,
>
> On 12/17/18 4:14 PM, Juergen Gross wrote:
> > This email only tracks big items for xen.git tree. Please reply for items you
> > would like to see in 4.12 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.
> >
> > [...]
> > = Projects =
> >
> > === x86 ===
>
> We (Tamas and us) would really like to see the "Fix VGA logdirty related
> display freezes with altp2m" series in 4.12.
>
> It is currently at V11 (AFAICT with a single outstanding issue to be
> clarified), waiting for comments from George.

Indeed, please add it to the tracked series list.

Thanks,
Tamas

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: Xen 4.12 Development Update [ In reply to ]
On Mon, 14 Jan 2019, Lars Kurth wrote:
> Hi Juergen,
>
> > On 14 Jan 2019, at 10:13, Juergen Gross <jgross@suse.com> wrote:
> >
> > This email only tracks big items for xen.git tree. Please reply for items you
> > would like to see in 4.12 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 about every 8 months.
> > The upcoming 4.12 timeline are as followed:
> >
> > * Last posting date: December 14th, 2018
> > Last posting date for patches touching ARM code: December 1st, 2018
> > * Hard code freeze: January 11th, 2019
> > Hard code freeze for patches touching ARM code: December 21st, 2018
> > --> we are here
> > * RC1: TBD
> > * Release: March 7th, 2019
> >
> > Note that we don't have freeze exception scheme anymore. All patches
> > that wish to go into 4.12 must be posted initially no later than the
> > last posting date and finally no later than the hard code freeze. All
> > patches posted after that date will be automatically queued into next
> > release.
> >
> > RCs will be arranged immediately after freeze.
>
> We should start planning on a Test Day schedule.
>
> > We recently introduced a jira instance to track all the tasks (not only big)
> > for the project. See: https://xenproject.atlassian.net/projects/XEN/issues.
> >
> > Some of the tasks tracked by this e-mail also have a corresponding jira task
> > referred by XEN-N.
> >
> > I have started to include the version number of series associated to each
> > feature. Can each owner send an update on the version number if the series
> > was posted upstream?
> >
> > = Projects =
> >
> > == Hypervisor ==
> >
> > * Improvements to domain creation (v2)
> > - Andrew Cooper
> >
> > * Argo (inter-VM communication) (v3)
> > - Christopher Clark
> >
> > * Core aware scheduling (RFC v1)
> > - Dario Faggioli
> >
> > * Core aware scheduling for credit2 (RFC v1)
> > - Dario Faggioli
> >
> > === x86 ===
> >
> > * hypervisor x86 instruction emulator additions for AVX512 (v7)
> > - Jan Beulich
> >
> > * qemu deprivilege (v4)
> > - George Dunlap
> >
> > * Fixes to #DB injection
> > - Andrew Cooper
> >
> > * CPUID/MSR Xen/toolstack improvements
> > - Andrew Cooper
> >
> > * Improvements to domain_crash()
> > - Andrew Cooper
> >
> > === ARM ===
> >
> > == Completed ==
> >
> > * guest resource mapping
> > - Paul Durrant
> >
> > * PV-only hypervisor
> > - Wei Liu
> >
> > * HVM-only hypervisor
> > - Wei Liu
> >
> > * Make credit2 scheduler the default
> > - George Dunlap
> >
> > * Grub2: Support PVH guest boot
> > - Juergen Gross
> >
> > * Fix VGA logdirty related display freezes with altp2m
> > - Razvan Cojocaru
> >
> > * dom0less (boot multiple domains from device tree)
> > - Stefano Stabellini
> >
> > * Implement Set/Way operations
> > - Julien Grall
>
> @Stefano:
> Didn't the ARM KCONFIG stuff go in *after* 4.11? If so, this should probably be added.
> Can't recall the series name

Yes, after 4.11. xen/arch/arm/configs/tiny64.conf is new in 4.12.


> Also, I think the Aggios changes went in after 4.11 was released also.
> The series was "xen/arm64: Suspend preconditions and CPU hotplug fixes"

Yes, that's right


> @ALL: also, for any major new features and/or enablers, we should look at the docs and make sure they are in place and up-to-date, that SUPPORT.md is updated and that any worthy/big enough features are listed. Also, if you contributed a larger series/feature and it is not on this list, please let us know.
>
> Thank you to everyone contributing to the project


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel