Xen 4.12 Development Update

Xen 4.12 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.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

*  Improvements to domain creation (v2)
  -  Andrew Cooper

=== x86 === 

*  guest resource mapping (v18)
  -  Paul Durrant

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

*  PV-IOMMU (v6)
  -  Paul Durrant

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

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

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

*  PV-only hypervisor (v1)
  -  Wei Liu

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

[Jan Beulich]

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

> *  PV-only hypervisor (v1)
>   -  Wei Liu

This surely has progressed past v1.

Jan



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

Re: Xen 4.12 Development Update

[Paul Durrant]

> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: 12 September 2018 09:21
> To: Paul Durrant <Paul.Durrant@citrix.com>; Juergen Gross
> <jgross@suse.com>
> Cc: xen-devel <xen-devel@lists.xenproject.org>
> Subject: Re: Xen 4.12 Development Update
> 
> >>> 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?

Yes, it has.

  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.
> 
> > *  PV-only hypervisor (v1)
> >   -  Wei Liu
> 
> This surely has progressed past v1.
> 
> Jan
> 


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

Re: Xen 4.12 Development Update

[Wei Liu]

On Wed, Sep 12, 2018 at 02:20:46AM -0600, 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.
> 
> > *  PV-only hypervisor (v1)
> >   -  Wei Liu
> 
> This surely has progressed past v1.

There will be further patches to maybe make things nicer, but at this
stage PV-only hypervisor is hopefully fully functional.

Wei.

> 
> Jan
> 
> 
> 
> _______________________________________________
> 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 4.12 Development Update

[Juergen Gross]

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

[Jan Beulich]

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

Xen 4.12 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.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 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


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

[Andrew Cooper]

On 14/01/2019 10:13, Juergen Gross wrote:
> 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

There is not realistically going to be further work done here in the
4.12 timeframe.

The work so far has fixed a load of NULL pointer dereferences for blind
uses of d->vcpu[], but a number still remain for blind uses of
d->vcpu[0].  You can still crash Xen by issuing specific toolstack
hypercalls between createdomain and maxvcpus, but its now far harder
than in 4.11

> === x86 === 
>
> *  Fixes to #DB injection
>   -  Andrew Cooper

Nor this.  There is a monitoring interaction issue I haven't got around
to fixing yet, and I've subsequently discovered that the way we inject
debug exceptions on VT-x is broken.  There is a specific passage in the
SDM which tells us not to do it the way we do, because otherwise we end
up with incorrect prioritisation of events when resuming the guest.

~Andrew

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

Re: Xen 4.12 Development Update

[Lars Kurth]

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

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"

@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

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

Re: Xen 4.12 Development Update

[Stefano Stabellini]

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

Xen 4.12 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.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
--> we are here
* Hard code freeze: January 11th, 2019
  Hard code freeze for patches touching ARM code: December 21st, 2018
* 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 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

*  Argo (inter-VM communication) (v1)
  -  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 (v6)
  -  Jan Beulich

*  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

*  qemu deprivilege (v4)
  -  George Dunlap

*  Improve late microcode loading (v4)
  -  Chao Gao

*  Fixes to #DB injection
  -  Andrew Cooper

*  CPUID/MSR Xen/toolstack improvements
  -  Andrew Cooper

*  Improvements to domain_crash()
  -  Andrew Cooper

=== ARM === 

*  dom0less (boot multiple domains from device tree) (v4)
  -  Stefano Stabellini

*  Implement Set/Way operations (RFC)
  -  Julien Grall

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

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


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

[Razvan Cojocaru]

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.


Thanks,
Razvan

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

Re: Xen 4.12 Development Update

[Tamas K Lengyel]

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

Xen 4.12 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.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
* RC1: TBD
* Release: March 7th, 2019

!!! Last posting date for patches touching ARM code is only 2 days away !!!

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

*  Argo (inter-VM communication)
  -  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 (v5)
  -  Jan Beulich

*  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

*  qemu deprivilege (v4)
  -  George Dunlap

*  Improve late microcode loading (v4)
  -  Chao Gao

*  Fixes to #DB injection
  -  Andrew Cooper

*  CPUID/MSR Xen/toolstack improvements
  -  Andrew Cooper

*  Improvements to domain_crash()
  -  Andrew Cooper

=== ARM === 

*  dom0less (boot multiple domains from device tree) (v4)
  -  Stefano Stabellini

*  Implement Set/Way operations (RFC)
  -  Julien Grall

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

== Grub2 == 

*  Support PVH guest boot (v5)
  -  Juergen Gross

== Completed == 

*  guest resource mapping
  -  Paul Durrant

*  PV-only hypervisor
  -  Wei Liu

*  HVM-only hypervisor
  -  Wei Liu

*  Make credit2 scheduler the default
  -  George Dunlap


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

[Andrew Cooper]

On 28/11/2018 10:26, Juergen Gross wrote:
> = Projects =
>
> == Hypervisor == 
>
> *  Improvements to domain creation (v2)
>   -  Andrew Cooper

Made a bit more progress.  Still plenty to do.

> === x86 === 
>
> *  Fixes to #DB injection
>   -  Andrew Cooper

Quickly turning into a rats nest.  Next task is to clean up the
monitor_*() calls so they can properly cope with avoiding re-entrant
triggering.

>
> *  CPUID/MSR Xen/toolstack improvements
>   -  Andrew Cooper

Again, made some progress.  The current task which is out on the mailing
list is to disentangle PVRDTSCP.

~Andrew

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

Re: Xen 4.12 Development Update

[Christopher Clark]

On Wed, Nov 28, 2018 at 2:26 AM Juergen Gross <jgross@suse.com> wrote:
>
> = Projects =
>
> == Hypervisor ==
>
> *  Argo (inter-VM communication)

I have a patch series for this that is approaching readiness to post.
It does touch ARM (slightly) so will be posted this week to meet the
ARM deadline.

Christopher

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

Re: Xen 4.12 Development Update

[Volodymyr Babchuk]

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?
I'm really aiming to add this feature to 4.12


-- 
WBR Volodymyr Babchuk aka lorc [+380976646013]
mailto: vlad.babchuk@gmail.com

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

Re: Xen 4.12 Development Update

[Juergen Gross]

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

Xen 4.12 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.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
* RC1: TBD
* Release: March 7th, 2019

!!! Last posting date for patches touching ARM code is only 2 days away !!!

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

*  Argo (inter-VM communication)
  -  Christopher Clark

*  Core aware scheduling (RFC v1)
  -  Dario Faggioli

=== x86 === 

*  hypervisor x86 instruction emulator additions for AVX512 (v5)
  -  Jan Beulich

*  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

*  qemu deprivilege (v4)
  -  George Dunlap

*  Improve late microcode loading (v4)
  -  Chao Gao

*  dom0less (boot multiple domains from device tree) (v4)
  -  Stefano Stabellini

== Grub2 == 

*  Support PVH guest boot (v5)
  -  Juergen Gross

== Completed == 

*  guest resource mapping
  -  Paul Durrant

*  PV-only hypervisor
  -  Wei Liu

*  HVM-only hypervisor
  -  Wei Liu

*  Make credit2 scheduler the default
  -  George Dunlap


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

[Juergen Gross]

Sorry, this one is missing some updates. Will resend soon.


Juergen

On 28/11/2018 11:15, 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.
> 
> = 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
> * RC1: TBD
> * Release: March 7th, 2019
> 
> !!! Last posting date for patches touching ARM code is only 2 days away !!!
> 
> 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 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
> 
> *  Argo (inter-VM communication)
>   -  Christopher Clark
> 
> *  Core aware scheduling (RFC v1)
>   -  Dario Faggioli
> 
> === x86 === 
> 
> *  hypervisor x86 instruction emulator additions for AVX512 (v5)
>   -  Jan Beulich
> 
> *  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
> 
> *  qemu deprivilege (v4)
>   -  George Dunlap
> 
> *  Improve late microcode loading (v4)
>   -  Chao Gao
> 
> *  dom0less (boot multiple domains from device tree) (v4)
>   -  Stefano Stabellini
> 
> == Grub2 == 
> 
> *  Support PVH guest boot (v5)
>   -  Juergen Gross
> 
> == Completed == 
> 
> *  guest resource mapping
>   -  Paul Durrant
> 
> *  PV-only hypervisor
>   -  Wei Liu
> 
> *  HVM-only hypervisor
>   -  Wei Liu
> 
> *  Make credit2 scheduler the default
>   -  George Dunlap
> 
> 
> 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 4.12 Development Update

[Paul Durrant]

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

There's no way this is going to make 4.12 now.

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

Xen 4.12 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.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
* 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

*  Improvements to domain creation (v2)
  -  Andrew Cooper

*  Argo (inter-VM communication)
  -  Christopher Clark

=== x86 === 

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

*  PV-IOMMU (v6)
  -  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

*  dom0less (boot multiple domains from device tree) (v4)
  -  Stefano Stabellini

== Grub2 == 

*  Support PVH guest boot (v4)
  -  Juergen Gross

== Completed == 

*  guest resource mapping
  -  Paul Durrant

*  PV-only hypervisor
  -  Wei Liu

*  Make credit2 scheduler the default
  -  George Dunlap


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

[Wei Liu]

On Fri, Nov 09, 2018 at 11:16:31AM +0100, Juergen Gross wrote:
> 
> == Completed == 

 * HVM-only hypervisor
   - Wei Liu

Wei.

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

Re: Xen 4.12 Development Update

[Jan Beulich]

>>> On 09.11.18 at 11:16, <jgross@suse.com> wrote:
> 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?

Oh, I had assumed you'd maintain this as things get posted.

> == Hypervisor == 
> 
> *  Per-cpu tasklet
>   -  XEN-28
>   -  Konrad Rzeszutek Wilk
> 
> *  Improvements to domain creation (v2)
>   -  Andrew Cooper
> 
> *  Argo (inter-VM communication)
>   -  Christopher Clark

Core aware scheduling (Dario)?

> === x86 === 
> 
> *  hypervisor x86 instruction emulator additions (v2)
>   -  Jan Beulich

This appears to refer to v4 of "x86emul: fixes, improvements, and
beginnings of AVX512 support" (which, despite its title, is now more
than 50% of the AVX512 work).

> *  PV-IOMMU (v6)
>   -  Paul Durrant

v7 was posted almost a month ago.

Jan



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

Re: Xen 4.12 Development Update

[Dario Faggioli]

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

On Fri, 2018-11-09 at 03:53 -0700, Jan Beulich wrote:
> > > > On 09.11.18 at 11:16, <jgross@suse.com> wrote:
> > == Hypervisor == 
> > 
> > *  Per-cpu tasklet
> >   -  XEN-28
> >   -  Konrad Rzeszutek Wilk
> > 
> > *  Improvements to domain creation (v2)
> >   -  Andrew Cooper
> > 
> > *  Argo (inter-VM communication)
> >   -  Christopher Clark
> 
> Core aware scheduling (Dario)?
>
Yes, indeed. Thanks Jan:

 *  Core aware scheduling for Credit2
   - Dario Faggioli

Status is RFC posted, waiting for feedback.

If I do get some feedback (and depending on the feedback itself, of
course :-D ) there are chances for such series to be ready in time.

The Credit1 one has, on the other hand, much smaller chances.

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

[-- 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 4.12 Development Update

[George Dunlap]

On 11/9/18 10:16 AM, 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.
> 
> = 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
> * 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.

Sorry, do you mean "...must be posted no later than the hard code freeze"?

Previously "Last posting date" has meant that as long as v1 was posted
before that date, vN can be checked in any time before the hard code
freeze.  Just checking to see that that's still the  meaning.

> = Projects =
> 
> == Hypervisor == 
> 
> *  Per-cpu tasklet
>   -  XEN-28
>   -  Konrad Rzeszutek Wilk
> 
> *  Improvements to domain creation (v2)
>   -  Andrew Cooper
> 
> *  Argo (inter-VM communication)
>   -  Christopher Clark
> 
> === x86 === 
> 
> *  hypervisor x86 instruction emulator additions (v2)
>   -  Jan Beulich
> 
> *  PV-IOMMU (v6)
>   -  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
> 
> *  dom0less (boot multiple domains from device tree) (v4)
>   -  Stefano Stabellini

You can add qemu-depriv to this list.  There's a reasonable chance that
it will be good enough for a "tech-preview" by Dec 14th.

Thanks,
 -George

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

Re: Xen 4.12 Development Update

[Juergen Gross]

On 09/11/2018 11:56, George Dunlap wrote:
> On 11/9/18 10:16 AM, 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.
>>
>> = 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
>> * 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.
> 
> Sorry, do you mean "...must be posted no later than the hard code freeze"?
> 
> Previously "Last posting date" has meant that as long as v1 was posted
> before that date, vN can be checked in any time before the hard code
> freeze.  Just checking to see that that's still the  meaning.

That's the wording used for the last couple releases.

What about:

"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."

> 
>> = Projects =
>>
>> == Hypervisor == 
>>
>> *  Per-cpu tasklet
>>   -  XEN-28
>>   -  Konrad Rzeszutek Wilk
>>
>> *  Improvements to domain creation (v2)
>>   -  Andrew Cooper
>>
>> *  Argo (inter-VM communication)
>>   -  Christopher Clark
>>
>> === x86 === 
>>
>> *  hypervisor x86 instruction emulator additions (v2)
>>   -  Jan Beulich
>>
>> *  PV-IOMMU (v6)
>>   -  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
>>
>> *  dom0less (boot multiple domains from device tree) (v4)
>>   -  Stefano Stabellini
> 
> You can add qemu-depriv to this list.  There's a reasonable chance that
> it will be good enough for a "tech-preview" by Dec 14th.

Okay.


Juergen

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

Re: Xen 4.12 Development Update

[George Dunlap]

On 11/9/18 11:07 AM, Juergen Gross wrote:
> On 09/11/2018 11:56, George Dunlap wrote:
>> On 11/9/18 10:16 AM, 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.
>>>
>>> = 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
>>> * 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.
>>
>> Sorry, do you mean "...must be posted no later than the hard code freeze"?
>>
>> Previously "Last posting date" has meant that as long as v1 was posted
>> before that date, vN can be checked in any time before the hard code
>> freeze.  Just checking to see that that's still the  meaning.
> 
> That's the wording used for the last couple releases.

Yes, and I'm sorry I haven't been paying very keen attention; I did this
time because I have something I may want to get in. :-)

> What about:
> 
> "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."

Yes, I think that's more clear, thanks.

 -George

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

Re: Xen 4.12 Development Update

[Andrew Cooper]

On 09/11/18 10:16, Juergen Gross wrote:
> = Projects =
>
> == Hypervisor == 
>
> *  Improvements to domain creation (v2)
>   -  Andrew Cooper

There is one known bug which definitely needs resolving before 4.12 goes
out.  Attempting to create a VM with 0 vcpus trips over a bad error path
when we try to remove permissions for an irq which we never gave in the
first place.  The fix is most likely to not change irq permissions on unmap.

Beyond that, the next actions are to make the create/destroy paths
idempotent.  If anyone feels like helping out here, please do.

After that, DOMCTL_max_vcpus needs to be folded into the create path.

An orthogonal task, which really also needs doing before 4.12 goes out
is to rearrange the point at which d->max_cpus is calculated, so ARM
gets this number early enough in construction to properly build the
GIC.  (At the moment, there is a bait-and-switch to defer GIC
construction until the first vcpu is being constructed).

> === x86 ===

* Fixes to #DB injection

This is also a swamp.  Already done:

1) Fixes to vcpu register initialisation

Still to do:

2) Rework monitor hooking to avoid livelocks with a fixed #DB
3) Plumb pending_dbg into x86_event, including reporting properly in monitor
4) Fix xen_dm_op_inject_event to audit its data rather than causing a
vmentry failure
5) Fix merging of new bits into %dr6
6) Fix singlestepping to not result in a vmentry failure when in an STI
shadow
$N) Pester Intel some more as to why a vmexit with both singlestep and
breakpoint events pending loses architectural information.

Also, the big one.

* CPUID/MSR Xen/toolstack improvements

This is blocking an enormous quantity of work, included but not limited to:

1) Fixing topology layout.  Unblocks the >127 vcpu work, and core-aware
scheduling work.
2) Virtusalising features which MSRs for configuration, including
nested-VTx, SGX, Intel PT and MSR_ARCH_CAPS.

~Andrew

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

Re: Xen 4.12 Development Update

[Andrew Cooper]

On 09/11/18 11:44, Andrew Cooper wrote:
> On 09/11/18 10:16, Juergen Gross wrote:
>> = Projects =
>>
>> == Hypervisor == 
>>
>> *  Improvements to domain creation (v2)
>>   -  Andrew Cooper
> There is one known bug which definitely needs resolving before 4.12 goes
> out.  Attempting to create a VM with 0 vcpus trips over a bad error path
> when we try to remove permissions for an irq which we never gave in the
> first place.  The fix is most likely to not change irq permissions on unmap.
>
> Beyond that, the next actions are to make the create/destroy paths
> idempotent.  If anyone feels like helping out here, please do.
>
> After that, DOMCTL_max_vcpus needs to be folded into the create path.
>
> An orthogonal task, which really also needs doing before 4.12 goes out
> is to rearrange the point at which d->max_cpus is calculated, so ARM
> gets this number early enough in construction to properly build the
> GIC.  (At the moment, there is a bait-and-switch to defer GIC
> construction until the first vcpu is being constructed).

Oh - another one I forgot.

* Improvements to domain_crash()

The purpose of this is to fix a livepatching bug, but it has the side
effect of fixing the fact that in release builds, most domain_crash()'s
have no clarifying information as to what went wrong.

I've posted about half the work.  What remains in the monolithic patch
to change domain_crash()'s API to make it printk-like.

~Andrew

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

Re: Xen 4.12 Development Update

[Julien Grall]

Hi Juergen,

On 09/11/2018 10:16, 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.
> 
> = 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
> * 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?

> *  dom0less (boot multiple domains from device tree) (v4)
>    -  Stefano Stabellini

This is Arm and not x86.

Other series for Arm:

Implement Set/Way operations (rfc)
    - Julien Grall

TEE mediator (and OP-TEE) support in XEN (v2)
    - Volodymyr_Babchuk@epam.com

Cheers,

-- 
Julien Grall

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

Xen 4.12 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.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

*  Improvements to domain creation (v2)
  -  Andrew Cooper

*  Argo (inter-VM communication)
  -  Christopher Clark

*  Make credit2 scheduler the default
  -  George Dunlap

=== x86 === 

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

*  PV-IOMMU (v6)
  -  Paul Durrant

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

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

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

== Grub2 == 

*  Support PVH guest boot (v1)
  -  Juergen Gross

== Completed == 

*  guest resource mapping
  -  Paul Durrant

*  PV-only hypervisor
  -  Wei Liu


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

[Chao Gao]

Hi Juergen,

"Improve late microcode loading" (v4) is expected to be merged in
Xen 4.12. Is it possible to add this series into the task list below?

On Mon, Oct 08, 2018 at 04:44:11PM +0800, 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.
>
>= 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
>
>*  Improvements to domain creation (v2)
>  -  Andrew Cooper
>
>*  Argo (inter-VM communication)
>  -  Christopher Clark
>
>*  Make credit2 scheduler the default
>  -  George Dunlap
>
>=== x86 ===
>
>*  hypervisor x86 instruction emulator additions (v2)
>  -  Jan Beulich
>
>*  PV-IOMMU (v6)
>  -  Paul Durrant
>
>*  HVM guest CPU topology support (RFC)
>  -  Chao Gao
>
>*  Intel Processor Trace virtualization enabling (v1)
>  -  Luwei Kang
>
>*  Linux stub domains (RFC)
>  -  Marek Marczykowski-Górecki
>
>== Grub2 ==
>
>*  Support PVH guest boot (v1)
>  -  Juergen Gross
>
>== Completed ==
>
>*  guest resource mapping
>  -  Paul Durrant
>
>*  PV-only hypervisor
>  -  Wei Liu
>
>
>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

Xen 4.12 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.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

[Rich Persaud]

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

> 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

[-- Attachment #1.2: Type: text/html, Size: 2150 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