[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

[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

*  x2APIC support for AMD (v2)
  -  Jan Beulich

*  EIBRS
  -  Andrew Cooper

== Completed == 

*  Drop tmem
  -  Wei Liu

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

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


Juergen Gross

_______________________________________________
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

[Jan Beulich]

On 01.07.2019 13:35, Juergen Gross wrote:
> === 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
> 
> *  x2APIC support for AMD (v2)
>    -  Jan Beulich
> 
> *  EIBRS
>    -  Andrew Cooper

Wasn't the AVX512 emulator work (now at v9) on this list earlier on?

Jan

_______________________________________________
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

[Juergen Gross]

On 01.07.19 13:42, Jan Beulich wrote:
> On 01.07.2019 13:35, Juergen Gross wrote:
>> === 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
>>
>> *  x2APIC support for AMD (v2)
>>     -  Jan Beulich
>>
>> *  EIBRS
>>     -  Andrew Cooper
> 
> Wasn't the AVX512 emulator work (now at v9) on this list earlier on?

Oh sorry, that was lost somehow.

Now re-added.


Juergen

_______________________________________________
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

[Volodymyr Babchuk]

Hi Juergen,

Juergen Gross writes:

> 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.
>
[...]
>
> == Completed ==
>
> *  Drop tmem
>   -  Wei Liu
>
> *  Add support for Hygon Dhyana Family 18h processor
>   -  Pu Wen
>
> *  TEE mediator (and OP-TEE) support in XEN
>   -  Volodymyr Babchuk

OP-TEE is not completely completed. Only patches to hypervisor were
merged. There are patches for toolstack and documentation still under
review.

--
Best regards,Volodymyr Babchuk
_______________________________________________
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 (v8)
  -  Chao Gao

*  Fixes to #DB injection
  -  Andrew Cooper

*  CPUID/MSR Xen/toolstack improvements
  -  Andrew Cooper

*  Improvements to domain_crash()
  -  Andrew Cooper

*  EIBRS
  -  Andrew Cooper

=== ARM === 

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

== Completed == 

*  Drop tmem
  -  Wei Liu

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

*  hypervisor x86 instruction emulator additions for AVX512
  -  Jan Beulich

*  x2APIC support for AMD
  -  Jan Beulich


Juergen Gross

_______________________________________________
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 01/08/2019 17:00, Juergen Gross wrote:
> == Hypervisor == 
>
> *  Improvements to domain creation (v2)
>   -  Andrew Cooper

This should probably be dropped.  Its not going to get a look in in the
forseeable future, and is in the position of gaining incremental
improvements anyway.

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

I expect this is unlikely to get further attention?

~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

[Wei Liu]

On Thu, 1 Aug 2019 at 17:48, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>
> On 01/08/2019 17:00, Juergen Gross wrote:
> > == Hypervisor ==
> >
> > *  Improvements to domain creation (v2)
> >   -  Andrew Cooper
>
> This should probably be dropped.  Its not going to get a look in in the
> forseeable future, and is in the position of gaining incremental
> improvements anyway.
>
> > *  Switch to use domheap page for page table (RFC v1)
> >   -  Wei Liu
>
> I expect this is unlikely to get further attention?
>

Not in the near future. Sorry.

Wei.

> ~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

[Roman Shaposhnik]

On Thu, Aug 1, 2019 at 9:01 AM 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.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?

Great timeline! On LF Edge Project EVE side, we'd like to help with testing an
upcoming 4.13 as much as we can. The goal for us is to get rid of out-of-tree
patches (most of them have to do with Alpine Linux support) and to make sure
that we don't have issue on any of these platforms:
     https://wiki.lfedge.org/display/EVE/Hardware+Platforms+Supporting+EVE

Since I'm still a little bit new to how Xen release process works, I'm wondering
what's the best way for us to stay on the same page with the rest of
the community
testing efforts?

Will there be nightly tarballs published at some point? Is there any
kind of build
infrastructure I can hook up on our side to make sure that I report issues as
soon as possible?

Thanks,
Roman.

>
> = 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 (v8)
>   -  Chao Gao
>
> *  Fixes to #DB injection
>   -  Andrew Cooper
>
> *  CPUID/MSR Xen/toolstack improvements
>   -  Andrew Cooper
>
> *  Improvements to domain_crash()
>   -  Andrew Cooper
>
> *  EIBRS
>   -  Andrew Cooper
>
> === ARM ===
>
> *  TEE mediator (and OP-TEE) support in XEN (v7)
>   -  Volodymyr Babchuk
>
> == Completed ==
>
> *  Drop tmem
>   -  Wei Liu
>
> *  Add support for Hygon Dhyana Family 18h processor
>   -  Pu Wen
>
> *  hypervisor x86 instruction emulator additions for AVX512
>   -  Jan Beulich
>
> *  x2APIC support for AMD
>   -  Jan Beulich
>
>
> Juergen Gross
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel

_______________________________________________
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

[Roger Pau Monné]

On Thu, Aug 01, 2019 at 11:11:50AM -0700, Roman Shaposhnik wrote:
> On Thu, Aug 1, 2019 at 9:01 AM 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.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?
> 
> Great timeline! On LF Edge Project EVE side, we'd like to help with testing an
> upcoming 4.13 as much as we can. The goal for us is to get rid of out-of-tree
> patches (most of them have to do with Alpine Linux support) and to make sure
> that we don't have issue on any of these platforms:
>      https://wiki.lfedge.org/display/EVE/Hardware+Platforms+Supporting+EVE

We currently have kind of different tests systems, we have Travis and
Gitlab CI build testing, which basically makes sure the build works on
a variety of OSes and toolchains. Gitlab CI also has a couple of
functional tests (by booting Xen in QEMU), but those are very minimal.

Then pushes to master are gatted by osstest [0], which is a Xen specific
test system. osstest manages a pool of hardware (both x86 and ARM) and
performs a wide variety of tests before declaring a given commit as
good. You can for example take a look at one of the recent osstest
reports on the staging branch:

https://lists.xenproject.org/archives/html/xen-devel/2019-08/msg00096.html

And:

http://logs.test-lab.xenproject.org/osstest/logs/139589/

Which contains the full test matrix.

> Since I'm still a little bit new to how Xen release process works, I'm wondering
> what's the best way for us to stay on the same page with the rest of
> the community
> testing efforts?

It's possible to integrate new hardware into osstest, but I think in
as a bare minimum it needs to be something that can be safely racked
in a datacenter and reliably operated without any human intervention.
I've added him to the Cc in case you have more specific questions
about this process.

> Will there be nightly tarballs published at some point? Is there any
> kind of build
> infrastructure I can hook up on our side to make sure that I report issues as
> soon as possible?

The release process will start with the code freeze, and afterwards
release candidates will be cut on a bi-weekly (or weekly?) basis. A
source code tarball is published for each of those. During the RC
process we ask users to test the release candidates and make sure all
the features they care about work properly, otherwise bug reports are
filled directly on the mailing list.

If you have the capacity and automation just testing staging or master
would also be helpful, since AFACT from the EVE supported platforms
you have a wide array of hardware to test on.

Thanks, Roger.

[0] http://xenbits.xen.org/gitweb/?p=osstest.git;a=summary

_______________________________________________
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

[Dario Faggioli]

[-- Attachment #1.1: Type: text/plain, Size: 1071 bytes --]

On Thu, 2019-08-01 at 18:00 +0200, Juergen Gross wrote:
> 
> = Projects =
> 
> == Hypervisor == 
> 
> [...]
>
> *  Core aware scheduling (RFC v1)
>   -  Dario Faggioli
> 
> *  Core aware scheduling for credit2 (RFC v1)
>   -  Dario Faggioli
> 
So, in theory, my patches can be made work on top of yours. And if one
does not work core-scheduling, but just core-aware scheduling, can boot
with sched-gran=cpu ("disabling" core-scheduling from Juergen's
patches) and with credit2-group-sched=core ("enabling" only core-aware
scheduling, from these patches.

For this very reason, I'm not throwing the code away. :-)

*However*, if this happens, I don't think it will be soon, and
definitely not for Xen 4.13.

So, I'd say we should drop these items from this list.

Regards
-- 
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
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

[Anthony PERARD]

On Thu, Aug 01, 2019 at 06:00:48PM +0200, Juergen Gross wrote:
> 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.

If I can be bold, I'd like to see some more QEMU depriv work going into
4.13. I'm not sure for the category, but maybe:

=== x86 ===

*  QEMU depriv, some libxl work (v2, v1, v1)
  -  Anthony PERARD

The different series currently on the list are:
- [v2] libxl: New slow lock + fix libxl_cdrom_insert with QEMU depriv
- [v1] Some cleanup of libxl
- [v1] libxl refactoring to use ev_qmp (with API changes)

Thanks,

-- 
Anthony PERARD

_______________________________________________
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

[Oleksandr]

Hello Juergen


I would like to see this in Xen 4.13:
https://lists.xenproject.org/archives/html/xen-devel/2019-08/msg00253.html


So, please add:

=== ARM ===

*  Renesas IPMMU-VMSA support + Linux's iommu_fwspec (V2)
   -  Oleksandr Tyshchenko

-- 
Regards,

Oleksandr Tyshchenko


_______________________________________________
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

[Paul Durrant]

> -----Original Message-----
> 
> === x86 ===
> 
> *  PV-IOMMU (v7)
>   -  Paul Durrant
> 

Realistically I'm unlikely to get back to the hypercall interface any time soon. There's just too much groundwork to lay, so probably better stop tracking this for now.

  Paul
_______________________________________________
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

*  Core scheduling (v2)
  -  Juergen Gross

=== 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 (v9)
  -  Chao Gao

*  Fixes to #DB injection
  -  Andrew Cooper

*  CPUID/MSR Xen/toolstack improvements
  -  Andrew Cooper

*  Improvements to domain_crash()
  -  Andrew Cooper

*  EIBRS
  -  Andrew Cooper

*  Xen ioreq server (v2)
  -  Roger Pau Monne

=== ARM === 

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

*  Renesas IPMMU-VMSA support + Linux's iommu_fwspec (v2)
  -  Oleksandr Tyshchenko

== Completed == 

*  Drop tmem
  -  Wei Liu

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

*  hypervisor x86 instruction emulator additions for AVX512
  -  Jan Beulich

*  x2APIC support for AMD
  -  Jan Beulich


Juergen Gross

_______________________________________________
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 06/09/2019 08:40, Juergen Gross wrote:
> 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

Wow this has crept up suddenly...

I'm going to braindump my "needs to be done for 4.13" list.

Before code freeze:
1) Refresh and repost MSR_VIRT_SPEC_CTRL.  Still very important for perf
on AMD Fam17h hardware.
2) Put together the "skeleton set_cpu_policy" plan.  This will help to
unblock some of the CPUID/MSR work, and will allow us to take
(/backport) MSR_ARCH_CAPS support, which is very critical for perf on
Intel Cascade Lake hardware.
2a) Stretch goal.  See about getting MSR_ARCH_CAPS working.  More likely
to be early in the 4.14 dev cycle and backport for 4.13.1
3) Stretch goal.  Dust off the domain_crash() changes which have been
pending for a couple of releases now.

Blockers:
1) L1TF_BARRIER mode.  What we have currently in tree takes a perf hit
while providing 0 security and breaking the ability to build livepatches
against 4.13.  My plan here is to put it behind an off-by-default
Kconfig option.
2) Get the Sphinx docs licensed as CC-BY, seeing as this is the first
release with them in.

Misc ought-to-haves:
1) Refresh and repost the "Introduction" and "wishlist" docs.
2) Post the conversion of xen-command-line.pandoc to sphinx which I've
been carrying locally rather too long now.

This should get the sphinx docs into a state of having several useful
bits in, even though we haven't moved over wholesale yet.

I've probably missed some things, but this should do for now.

~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

[Konrad Rzeszutek Wilk]

> == Hypervisor == 
> 
> *  Per-cpu tasklet
>   -  XEN-28
>   -  Konrad Rzeszutek Wilk

I haven't gotten to them since the posting three years ago?

I don't think I will get to them anytime soom too :-(

Would love if someone took them over..

P.S:
http://xenbits.xen.org/gitweb/?p=people/konradwilk/xen.git;a=shortlog;h=refs/heads/percpu_tasklet.v4.8.v2

_______________________________________________
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

[Paul Durrant]

> -----Original Message-----
[snip]
> 
> === x86 ===
> 
> *  PV-IOMMU (v7)
>   -  Paul Durrant

This is not happening, but I will be posting v9 of my "add per-domain IOMMU control" series fairly shortly.

  Paul
_______________________________________________
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

[Chao Gao]

On Fri, Sep 06, 2019 at 09:40:58AM +0200, Juergen Gross wrote:
>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.
>
>=== x86 === 
>
>*  HVM guest CPU topology support (RFC)
>  -  Chao Gao

No plan to continue this one due to some reason. Please drop this one.

>
>*  Improve late microcode loading (v9)
>  -  Chao Gao
>

Working on the v10. I would like to get it merged in 4.13.

Thanks
Chao

_______________________________________________
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

[Roman Shaposhnik]

Hi!

On Fri, Sep 6, 2019 at 12:41 AM 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.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

Naive question perhaps, but since the first deadline is two days away,
I'm wondering
what's my best option to provide early feedback? Currently we're testing with
master branch in Project EVE, but I've noticed that it is 4 weeks behind staging
at this point.

When is it expected to catch up?

> * 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
>
> *  Core scheduling (v2)
>   -  Juergen Gross
>
> === 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 (v9)
>   -  Chao Gao
>
> *  Fixes to #DB injection
>   -  Andrew Cooper
>
> *  CPUID/MSR Xen/toolstack improvements
>   -  Andrew Cooper
>
> *  Improvements to domain_crash()
>   -  Andrew Cooper
>
> *  EIBRS
>   -  Andrew Cooper
>
> *  Xen ioreq server (v2)
>   -  Roger Pau Monne
>
> === ARM ===
>
> *  TEE mediator (and OP-TEE) support in XEN (v7)
>   -  Volodymyr Babchuk
>
> *  Renesas IPMMU-VMSA support + Linux's iommu_fwspec (v2)
>   -  Oleksandr Tyshchenko
>
> == Completed ==
>
> *  Drop tmem
>   -  Wei Liu
>
> *  Add support for Hygon Dhyana Family 18h processor
>   -  Pu Wen
>
> *  hypervisor x86 instruction emulator additions for AVX512
>   -  Jan Beulich
>
> *  x2APIC support for AMD
>   -  Jan Beulich
>
>
> Juergen Gross
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel

_______________________________________________
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

[Juergen Gross]

On 12.09.19 08:10, Roman Shaposhnik wrote:
> Hi!
> 
> On Fri, Sep 6, 2019 at 12:41 AM 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.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
> 
> Naive question perhaps, but since the first deadline is two days away,
> I'm wondering
> what's my best option to provide early feedback? Currently we're testing with
> master branch in Project EVE, but I've noticed that it is 4 weeks behind staging
> at this point.
> 
> When is it expected to catch up?

As soon as OSStest is succeeding on staging.

Any feedback is very welcome, of course. In case you could base your
tests on staging this might speed up things, depending on your tests
(failing for the same reasons as OSStest wouldn't add that much
information, but finding other bugs would be a big plus).

In the RC-phase master should be rather close to staging, as a new RC
is always tagged on the master branch and staging should receive fixes
only (there are some exceptions from time to time, like security fixes).


Juergen

_______________________________________________
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

[Oleksandr]

Hi, Juergen

I have just pushed new version, so please update


=== ARM ===

*  Renesas IPMMU-VMSA support + Linux's iommu_fwspec (V4)
    -  Oleksandr Tyshchenko


-- 
Regards,

Oleksandr Tyshchenko


_______________________________________________
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]

As multiple rather important patch series are very short before being ready
I have decided to push the hard code freeze one week back to October 4th.

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
---> We are here
* Hard code freeze: October 4th, 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 == 

*  Core scheduling (v4)
  -  Juergen Gross

=== x86 === 

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

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

*  Improve late microcode loading (v12)
  -  Chao Gao

*  Fixes to #DB injection
  -  Andrew Cooper

*  CPUID/MSR Xen/toolstack improvements
  -  Andrew Cooper

*  Improvements to domain_crash()
  -  Andrew Cooper

*  EIBRS
  -  Andrew Cooper

*  Xen ioreq server (v2)
  -  Roger Pau Monne

=== ARM === 

== Completed == 

*  Drop tmem
  -  Wei Liu

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

*  hypervisor x86 instruction emulator additions for AVX512
  -  Jan Beulich

*  x2APIC support for AMD
  -  Jan Beulich

*  add per-domain IOMMU control
  -  Paul Durrant

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

*  Renesas IPMMU-VMSA support + Linux's iommu_fwspec
  -  Oleksandr Tyshchenko


Juergen Gross

_______________________________________________
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

[Steven Haigh]

At the risk of sounding like a broken record, is there an progress with 
investigations on the AMD Ryzen 3xxx series and Windows HVM systems?
Steven Haigh

📧 netwiz@crc.id.au     💻 https://www.crc.id.au
📞 +613 9001 6090       📱 +614 1293 5897


On Sat, Sep 28, 2019 at 07:09, Juergen Gross <jgross@suse.com> wrote:
> As multiple rather important patch series are very short before being 
> ready
> I have decided to push the hard code freeze one week back to October 
> 4th.
> 
> 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
> ---> We are here
> * Hard code freeze: October 4th, 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 ==
> 
> *  Core scheduling (v4)
>   -  Juergen Gross
> 
> === x86 ===
> 
> *  Intel Processor Trace virtualization enabling (v1)
>   -  Luwei Kang
> 
> *  Linux stub domains (RFC v2)
>   -  Marek Marczykowski-Górecki
> 
> *  Improve late microcode loading (v12)
>   -  Chao Gao
> 
> *  Fixes to #DB injection
>   -  Andrew Cooper
> 
> *  CPUID/MSR Xen/toolstack improvements
>   -  Andrew Cooper
> 
> *  Improvements to domain_crash()
>   -  Andrew Cooper
> 
> *  EIBRS
>   -  Andrew Cooper
> 
> *  Xen ioreq server (v2)
>   -  Roger Pau Monne
> 
> === ARM ===
> 
> == Completed ==
> 
> *  Drop tmem
>   -  Wei Liu
> 
> *  Add support for Hygon Dhyana Family 18h processor
>   -  Pu Wen
> 
> *  hypervisor x86 instruction emulator additions for AVX512
>   -  Jan Beulich
> 
> *  x2APIC support for AMD
>   -  Jan Beulich
> 
> *  add per-domain IOMMU control
>   -  Paul Durrant
> 
> *  TEE mediator (and OP-TEE) support in XEN
>   -  Volodymyr Babchuk
> 
> *  Renesas IPMMU-VMSA support + Linux's iommu_fwspec
>   -  Oleksandr Tyshchenko
> 
> 
> Juergen Gross
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel



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