[ANNOUNCE] Xen 4.13 Development Update

[ANNOUNCE] Xen 4.13 Development Update

[Juergen Gross]

This email only tracks big items for xen.git tree. Please reply for items you
would like to see in 4.13 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.13 timeline are as followed:

* Last posting date: September 13th, 2019
* Hard code freeze: September 27th, 2019
* RC1: TBD
* Release: November 7th, 2019

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

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

*  Improvements to domain creation (v2)
  -  Andrew Cooper

*  Core aware scheduling (RFC v1)
  -  Dario Faggioli

*  Core aware scheduling for credit2 (RFC v1)
  -  Dario Faggioli

*  Core scheduling (v1)
  -  Juergen Gross

*  Switch to use domheap page for page table (RFC v1)
  -  Wei Liu

=== x86 === 

*  PV-IOMMU (v7)
  -  Paul Durrant

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

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

*  Linux stub domains (RFC v2)
  -  Marek Marczykowski-Górecki

*  Improve late microcode loading (v7)
  -  Chao Gao

*  Fixes to #DB injection
  -  Andrew Cooper

*  CPUID/MSR Xen/toolstack improvements
  -  Andrew Cooper

*  Improvements to domain_crash()
  -  Andrew Cooper

*  Add support for Hygon Dhyana Family 18h processor (v4)
  -  Pu Wen

*  x2APIC support for AMD
  -  Jan Beulich

*  EIBRS
  -  Andrew Cooper

=== ARM === 

*  TEE mediator (and OP-TEE) support in XEN (v2)
  -  Volodymyr Babchuk

== Completed == 

*  Drop tmem
  -  Wei Liu


Juergen Gross

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

[Xen-devel] [ANNOUNCE] Xen 4.13 Development Update

[Juergen Gross]

This email only tracks big items for xen.git tree. Please reply for items you
would like to see in 4.13 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.13 timeline are as followed:

* Last posting date: September 13th, 2019
* Hard code freeze: September 27th, 2019
* RC1: TBD
* Release: November 7th, 2019

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

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

*  Improvements to domain creation (v2)
  -  Andrew Cooper

*  Core aware scheduling (RFC v1)
  -  Dario Faggioli

*  Core aware scheduling for credit2 (RFC v1)
  -  Dario Faggioli

*  Core scheduling (v1)
  -  Juergen Gross

*  Switch to use domheap page for page table (RFC v1)
  -  Wei Liu

=== x86 === 

*  PV-IOMMU (v7)
  -  Paul Durrant

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

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

*  Linux stub domains (RFC v2)
  -  Marek Marczykowski-Górecki

*  Improve late microcode loading (v7)
  -  Chao Gao

*  Fixes to #DB injection
  -  Andrew Cooper

*  CPUID/MSR Xen/toolstack improvements
  -  Andrew Cooper

*  Improvements to domain_crash()
  -  Andrew Cooper

*  Add support for Hygon Dhyana Family 18h processor (v4)
  -  Pu Wen

*  x2APIC support for AMD
  -  Jan Beulich

*  EIBRS
  -  Andrew Cooper

=== ARM === 

*  TEE mediator (and OP-TEE) support in XEN (v2)
  -  Volodymyr Babchuk

== Completed == 

*  Drop tmem
  -  Wei Liu


Juergen Gross

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

Re: [ANNOUNCE] Xen 4.13 Development Update

[Tamas K Lengyel]

> *  Improvements to domain creation (v2)
>   -  Andrew Cooper

Hi Andrew,
could you point me to a git branch where you have this work? I'm
experimenting with some stuff and would like to see what your work in
this area touches.

Thanks,
Tamas

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

Re: [Xen-devel] [ANNOUNCE] Xen 4.13 Development Update

[Tamas K Lengyel]

> *  Improvements to domain creation (v2)
>   -  Andrew Cooper

Hi Andrew,
could you point me to a git branch where you have this work? I'm
experimenting with some stuff and would like to see what your work in
this area touches.

Thanks,
Tamas

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

Re: [ANNOUNCE] Xen 4.13 Development Update

[Andrew Cooper]

On 28/05/2019 14:44, Tamas K Lengyel wrote:
>> *  Improvements to domain creation (v2)
>>   -  Andrew Cooper
> Hi Andrew,
> could you point me to a git branch where you have this work? I'm
> experimenting with some stuff and would like to see what your work in
> this area touches.

There is essentially nothing which isn't already in staging.  Suffice it
to say that MDS got in the way of continuing that work.

The next task on the list is to make the vcpu/domain destroy paths
idempotent, then reimplement the create paths by just returning out of
the top of the call tree with an error, and having the top level call
destroy.  This avoids having two different sets of destruction logic
which aren't quite identical.

With that in place, I can move the vcpu allocation loop into
domain_create() after which it will be impossible to find a domain by ID
and trip over some NULL vcpu pointers.

If you are introducing or adjusting allocation/deallocation logic,
please make the deallocation idempotent, and ideally use the deallocate
function to clean up from a failed allocate.  There will be some
tree-wide refactoring at some point in the future which moves everything
into place.  Until then, have at it.

~Andrew

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

Re: [Xen-devel] [ANNOUNCE] Xen 4.13 Development Update

[Andrew Cooper]

On 28/05/2019 14:44, Tamas K Lengyel wrote:
>> *  Improvements to domain creation (v2)
>>   -  Andrew Cooper
> Hi Andrew,
> could you point me to a git branch where you have this work? I'm
> experimenting with some stuff and would like to see what your work in
> this area touches.

There is essentially nothing which isn't already in staging.  Suffice it
to say that MDS got in the way of continuing that work.

The next task on the list is to make the vcpu/domain destroy paths
idempotent, then reimplement the create paths by just returning out of
the top of the call tree with an error, and having the top level call
destroy.  This avoids having two different sets of destruction logic
which aren't quite identical.

With that in place, I can move the vcpu allocation loop into
domain_create() after which it will be impossible to find a domain by ID
and trip over some NULL vcpu pointers.

If you are introducing or adjusting allocation/deallocation logic,
please make the deallocation idempotent, and ideally use the deallocate
function to clean up from a failed allocate.  There will be some
tree-wide refactoring at some point in the future which moves everything
into place.  Until then, have at it.

~Andrew

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