Re: [Xen-devel] Xen 4.10 Development update: code freeze date

[Julien Grall]

Hi all,

Quick reminder, the code freeze is tomorrow (Wednesday).

Please check-in everything by end of the day tomorrow. An RC will be cut 
on we get a push.


Cheers,

On 26/09/17 16:22, Julien Grall wrote:

Hi all,

The hard code freeze date will be extended by a week and half. I still 
expect Xen 4.10 released on time.


The new schedule is:
 * Code freeze: October 11th, 2017
 * RC1: TBD
 * Release:  December 2nd, 2017

Note that the last posting date has already past. All new series posted 
will be queued for the next release.


Cheers,



--
Julien Grall

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Yu Zhang]

On 8/22/2017 8:44 PM, Julien Grall wrote:

Hi,

On 22/08/17 11:22, Yu Zhang wrote:



On 8/21/2017 6:15 PM, Julien Grall wrote:

Hi Paul,

On 21/08/17 11:11, Paul Durrant wrote:

-Original Message-
From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
Julien Grall
Sent: 21 August 2017 11:08
To: xen-de...@lists.xenproject.org
Cc: julien.gr...@arm.com
Subject: [Xen-devel] Xen 4.10 Development Update

This email only tracks big items for xen.git tree. Please reply for
items you
woulk like to see in 4.10 so that people have an idea what is going
on and
prioritise accordingly.

You're welcome to provide description and use cases of the feature
you're
working on.

= Timeline =

We now adopt a fixed cut-off date scheme. We will release twice a
year. The upcoming 4.10 timeline are as followed:

* Last posting date: September 15th, 2017
* Hard code freeze: September 29th, 2017
* RC1: TBD
* Release: December 2, 2017

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

*  Add support of rcu_idle_{enter,exit}
  -  XEN-27
  -  Dario Faggioli

=== x86 ===

*  Allow ioreq server interface to support XenGT (v7)
  -  XEN-43
  -  Yu Zhang
  -  Paul Durrant


I think this is either done or obsolete now. Not sure which.


CCed Yu Zhang to tell which one.



Thanks, Julien. This is done now. :)


I may have messed up with the update. Was it upstreamed for Xen 4.9 or 
Xen 4.10? For the former, I will just totally remove it from the update.


It was merged in Xen 4.9. We can just remove this from the update. :-)

Thanks
Yu



Cheers,




___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Meng Xu]

On Mon, Aug 21, 2017 at 6:07 AM, Julien Grall  wrote:
> This email only tracks big items for xen.git tree. Please reply for items you
> woulk like to see in 4.10 so that people have an idea what is going on and
> prioritise accordingly.
>
> You're welcome to provide description and use cases of the feature you're
> working on.
>
> = Timeline =
>
> We now adopt a fixed cut-off date scheme. We will release twice a
> year. The upcoming 4.10 timeline are as followed:
>
> * Last posting date: September 15th, 2017
> * Hard code freeze: September 29th, 2017
> * RC1: TBD
> * Release: December 2, 2017
>
> Note that we don't have freeze exception scheme anymore. All patches
> that wish to go into 4.10 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
>
> *  Add support of rcu_idle_{enter,exit}
>   -  XEN-27
>   -  Dario Faggioli

I'm moving the RTDS scheduler to work-conserving scheduler.
The first version of the patch series has been posted at
https://www.mail-archive.com/xen-devel@lists.xen.org/msg117062.html,
after we discussed the RFC patch.

Thanks,

Meng

-- 
---
Meng Xu
PhD Candidate in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Julien Grall]

Hi,

On 22/08/17 11:22, Yu Zhang wrote:



On 8/21/2017 6:15 PM, Julien Grall wrote:

Hi Paul,

On 21/08/17 11:11, Paul Durrant wrote:

-Original Message-
From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
Julien Grall
Sent: 21 August 2017 11:08
To: xen-de...@lists.xenproject.org
Cc: julien.gr...@arm.com
Subject: [Xen-devel] Xen 4.10 Development Update

This email only tracks big items for xen.git tree. Please reply for
items you
woulk like to see in 4.10 so that people have an idea what is going
on and
prioritise accordingly.

You're welcome to provide description and use cases of the feature
you're
working on.

= Timeline =

We now adopt a fixed cut-off date scheme. We will release twice a
year. The upcoming 4.10 timeline are as followed:

* Last posting date: September 15th, 2017
* Hard code freeze: September 29th, 2017
* RC1: TBD
* Release: December 2, 2017

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

*  Add support of rcu_idle_{enter,exit}
  -  XEN-27
  -  Dario Faggioli

=== x86 ===

*  Allow ioreq server interface to support XenGT (v7)
  -  XEN-43
  -  Yu Zhang
  -  Paul Durrant


I think this is either done or obsolete now. Not sure which.


CCed Yu Zhang to tell which one.



Thanks, Julien. This is done now. :)


I may have messed up with the update. Was it upstreamed for Xen 4.9 or 
Xen 4.10? For the former, I will just totally remove it from the update.


Cheers,

--
Julien Grall

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Julien Grall]

On 22/08/17 06:59, Oleksandr Andrushchenko wrote:

Hi, Julien!


Hi Oleksandr,


On 08/21/2017 01:07 PM, Julien Grall wrote:

This email only tracks big items for xen.git tree. Please reply for
items you
woulk like to see in 4.10 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.


== Toolstack ==


we are working on adding support for sound/display/mtouch
into libxl/xl: display support patches + framework
refactoring patches are on review now: Oleksandr Grytsov is in charge
Patch set version: 4


I would keep that under the PV drivers. No need to have separate items 
for it :).



== PV Drivers ==

*  Multi-touch
   -  Oleksandr Andrushchenko
   -  Oleksanr Grytsov

nothing to be done in Xen, mtouch support is already
in the Linux kernel. We are not considering QEMU's backend atm


*  Sound
   -  Oleksandr Andrushchenko
   -  Oleksanr Grytsov

nothing to be done in Xen atm, Linux kernel frontend
is on review now - may need interface extension
Patch set version: initial

*  Display
   -  Oleksandr Andrushchenko
   -  Oleksanr Grytsov

nothing to be done in Xen atm, Linux frontend is not yet
ready to be upstreamed


Thank you for the update!

Cheers,

--
Julien Grall

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Yu Zhang]

On 8/21/2017 6:15 PM, Julien Grall wrote:

Hi Paul,

On 21/08/17 11:11, Paul Durrant wrote:

-Original Message-
From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
Julien Grall
Sent: 21 August 2017 11:08
To: xen-de...@lists.xenproject.org
Cc: julien.gr...@arm.com
Subject: [Xen-devel] Xen 4.10 Development Update

This email only tracks big items for xen.git tree. Please reply for 
items you
woulk like to see in 4.10 so that people have an idea what is going 
on and

prioritise accordingly.

You're welcome to provide description and use cases of the feature 
you're

working on.

= Timeline =

We now adopt a fixed cut-off date scheme. We will release twice a
year. The upcoming 4.10 timeline are as followed:

* Last posting date: September 15th, 2017
* Hard code freeze: September 29th, 2017
* RC1: TBD
* Release: December 2, 2017

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

*  Add support of rcu_idle_{enter,exit}
  -  XEN-27
  -  Dario Faggioli

=== x86 ===

*  Allow ioreq server interface to support XenGT (v7)
  -  XEN-43
  -  Yu Zhang
  -  Paul Durrant


I think this is either done or obsolete now. Not sure which.


CCed Yu Zhang to tell which one.



Thanks, Julien. This is done now. :)

Yu


Cheers,




___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Oleksandr Andrushchenko]

Hi, Julien!

On 08/21/2017 01:07 PM, Julien Grall wrote:

This email only tracks big items for xen.git tree. Please reply for items you
woulk like to see in 4.10 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.


== Toolstack ==


we are working on adding support for sound/display/mtouch
into libxl/xl: display support patches + framework
refactoring patches are on review now: Oleksandr Grytsov is in charge
Patch set version: 4

== PV Drivers ==

*  Multi-touch
   -  Oleksandr Andrushchenko
   -  Oleksanr Grytsov

nothing to be done in Xen, mtouch support is already
in the Linux kernel. We are not considering QEMU's backend atm


*  Sound
   -  Oleksandr Andrushchenko
   -  Oleksanr Grytsov

nothing to be done in Xen atm, Linux kernel frontend
is on review now - may need interface extension
Patch set version: initial

*  Display
   -  Oleksandr Andrushchenko
   -  Oleksanr Grytsov

nothing to be done in Xen atm, Linux frontend is not yet
ready to be upstreamed

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel



___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Konrad Rzeszutek Wilk]

On Mon, Aug 21, 2017 at 11:07:39AM +0100, Julien Grall wrote:
> This email only tracks big items for xen.git tree. Please reply for items you
> woulk like to see in 4.10 so that people have an idea what is going on and
> prioritise accordingly.
> 
> You're welcome to provide description and use cases of the feature you're
> working on.
> 
> = Timeline =
> 
> We now adopt a fixed cut-off date scheme. We will release twice a
> year. The upcoming 4.10 timeline are as followed:
> 
> * Last posting date: September 15th, 2017
> * Hard code freeze: September 29th, 2017
> * RC1: TBD
> * Release: December 2, 2017
> 
> Note that we don't have freeze exception scheme anymore. All patches
> that wish to go into 4.10 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

I am not going to be able to get this done in the time-frame.
If somebody would be interested in picking up the patches I would
be thrilled!

(In the mean-time I have some livepatch patches that I am massaging).

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Jan Beulich]

>>> On 21.08.17 at 12:07,  wrote:
> *  Completion of the x86 insn emulator (as far as possible)
>   -  XEN-46
>   -  Jan Beulich

Patches for the next step have been pending unreviewed for
exactly 2 months. Considering how much review of new
functionality patches by various people I've been doing during
that period of time (not to speak of how much more is waiting
to be reviewed), I find it really unacceptable that such a series
is bottlenecked by having to wait for a single person (Andrew) to
review it. I can fully understand that he has no time to look
through this (non-trivial) series. Others should finally start
stepping up (and not just for pieces where review is easy and can
be done in a few minutes). Otherwise I may find myself forced to
stop reviewing any new functionality patches contributed by
people not otherwise participating in development in meaningful
ways (which would dramatically shrink my to-be-reviewed queue).

I did bring up in the past the theoretically possible model of
contributors having to build up credit for submitting new
functionality patches. Looking at the patch submission rate I
think this needs to be considered seriously, despite its very
obvious drawbacks.

Jan


___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Juergen Gross]

On 21/08/17 12:07, Julien Grall wrote:
> This email only tracks big items for xen.git tree. Please reply for items you
> woulk like to see in 4.10 so that people have an idea what is going on and
> prioritise accordingly.
> 
> You're welcome to provide description and use cases of the feature you're
> working on.
> 
> = Timeline =
> 
> We now adopt a fixed cut-off date scheme. We will release twice a
> year. The upcoming 4.10 timeline are as followed:
> 
> * Last posting date: September 15th, 2017
> * Hard code freeze: September 29th, 2017
> * RC1: TBD
> * Release: December 2, 2017
> 
> Note that we don't have freeze exception scheme anymore. All patches
> that wish to go into 4.10 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
> 
> *  Add support of rcu_idle_{enter,exit}
>   -  XEN-27
>   -  Dario Faggioli

*  Add support for modifying hyperviro parameters at runtime
  -  Juergen Gross


Juergen

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Julien Grall]

Hi Paul,

On 21/08/17 11:11, Paul Durrant wrote:

-Original Message-
From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
Julien Grall
Sent: 21 August 2017 11:08
To: xen-de...@lists.xenproject.org
Cc: julien.gr...@arm.com
Subject: [Xen-devel] Xen 4.10 Development Update

This email only tracks big items for xen.git tree. Please reply for items you
woulk like to see in 4.10 so that people have an idea what is going on and
prioritise accordingly.

You're welcome to provide description and use cases of the feature you're
working on.

= Timeline =

We now adopt a fixed cut-off date scheme. We will release twice a
year. The upcoming 4.10 timeline are as followed:

* Last posting date: September 15th, 2017
* Hard code freeze: September 29th, 2017
* RC1: TBD
* Release: December 2, 2017

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

*  Add support of rcu_idle_{enter,exit}
  -  XEN-27
  -  Dario Faggioli

=== x86 ===

*  Allow ioreq server interface to support XenGT (v7)
  -  XEN-43
  -  Yu Zhang
  -  Paul Durrant


I think this is either done or obsolete now. Not sure which.


CCed Yu Zhang to tell which one.

Cheers,

--
Julien Grall

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Paul Durrant]

> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
> Julien Grall
> Sent: 21 August 2017 11:08
> To: xen-de...@lists.xenproject.org
> Cc: julien.gr...@arm.com
> Subject: [Xen-devel] Xen 4.10 Development Update
> 
> This email only tracks big items for xen.git tree. Please reply for items you
> woulk like to see in 4.10 so that people have an idea what is going on and
> prioritise accordingly.
> 
> You're welcome to provide description and use cases of the feature you're
> working on.
> 
> = Timeline =
> 
> We now adopt a fixed cut-off date scheme. We will release twice a
> year. The upcoming 4.10 timeline are as followed:
> 
> * Last posting date: September 15th, 2017
> * Hard code freeze: September 29th, 2017
> * RC1: TBD
> * Release: December 2, 2017
> 
> Note that we don't have freeze exception scheme anymore. All patches
> that wish to go into 4.10 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
> 
> *  Add support of rcu_idle_{enter,exit}
>   -  XEN-27
>   -  Dario Faggioli
> 
> === x86 ===
> 
> *  Allow ioreq server interface to support XenGT (v7)
>   -  XEN-43
>   -  Yu Zhang
>   -  Paul Durrant

I think this is either done or obsolete now. Not sure which.

  Paul

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Oleksandr Tyshchenko]

Hi, Julien

On Thu, Jul 20, 2017 at 8:27 PM, Julien Grall  wrote:
> On 20/07/17 17:57, Manish Jaggi wrote:
>>
>> Hi Julien,
>
>
> Hello Manish,
>
> I am not sure why piggyback on Daniel Kiper as it is not related to your
> work...
>
>
>>> On Mon, Jul 17, 2017 at 02:26:22PM +0100, Julien Grall wrote:

 This email only tracks big items for xen.git tree. Please reply for
 items you
 woulk like to see in 4.10 so that people have an idea what is going
 on and
 prioritise accordingly.

 You're welcome to provide description and use cases of the feature
 you're
 working on.

 = Timeline =

 We now adopt a fixed cut-off date scheme. We will release twice a
 year. The upcoming 4.10 timeline are as followed:

 * Last posting date: September 15th, 2017
 * Hard code freeze: September 29th, 2017
 * RC1: TBD
 * Release: December 2, 2017

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

 *  Add support of rcu_idle_{enter,exit}
-  XEN-27
-  Dario Faggioli

 === x86 ===
>
>
> ... and answer on x86 category when your items look ARM specific.
>
>> I am working on XEN-70, have already posted rfc. [1]
>>
>> Also can you please add a xen-jira issue for the ITS ACPI support [2] v2
>> patches,
>> which I have already sent and am working on next rev.
>
>
> This is already existing in Jira. See XEN-75.
>
> But as said at the beginning of the e-mail, this is only tracking big
> features. We can't possible track all small items as the mail would become
> too long.
>
> I don't consider the two features you mention as big and don't see the need
> to track them here. But they are already tracked in Jira.
>
> Cheers,
>
> --
> Julien Grall
>
>
> ___
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel

Please add

=== ARM ===

*  Non-shared IOMMU support (v2)
  -  Oleksandr Tyshchenko

*  IPMMU-VMSA support (RFC)
  -  Oleksandr Tyshchenko

-- 
Regards,

Oleksandr Tyshchenko

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Julien Grall]

On 20/07/17 17:57, Manish Jaggi wrote:

Hi Julien,


Hello Manish,

I am not sure why piggyback on Daniel Kiper as it is not related to your 
work...



On Mon, Jul 17, 2017 at 02:26:22PM +0100, Julien Grall wrote:

This email only tracks big items for xen.git tree. Please reply for
items you
woulk like to see in 4.10 so that people have an idea what is going
on and
prioritise accordingly.

You're welcome to provide description and use cases of the feature
you're
working on.

= Timeline =

We now adopt a fixed cut-off date scheme. We will release twice a
year. The upcoming 4.10 timeline are as followed:

* Last posting date: September 15th, 2017
* Hard code freeze: September 29th, 2017
* RC1: TBD
* Release: December 2, 2017

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

*  Add support of rcu_idle_{enter,exit}
   -  XEN-27
   -  Dario Faggioli

=== x86 ===


... and answer on x86 category when your items look ARM specific.


I am working on XEN-70, have already posted rfc. [1]

Also can you please add a xen-jira issue for the ITS ACPI support [2] v2
patches,
which I have already sent and am working on next rev.


This is already existing in Jira. See XEN-75.

But as said at the beginning of the e-mail, this is only tracking big 
features. We can't possible track all small items as the mail would 
become too long.


I don't consider the two features you mention as big and don't see the 
need to track them here. But they are already tracked in Jira.


Cheers,

--
Julien Grall

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Manish Jaggi]

Hi Julien,

On Mon, Jul 17, 2017 at 02:26:22PM +0100, Julien Grall wrote:

This email only tracks big items for xen.git tree. Please reply for items you
woulk like to see in 4.10 so that people have an idea what is going on and
prioritise accordingly.

You're welcome to provide description and use cases of the feature you're
working on.

= Timeline =

We now adopt a fixed cut-off date scheme. We will release twice a
year. The upcoming 4.10 timeline are as followed:

* Last posting date: September 15th, 2017
* Hard code freeze: September 29th, 2017
* RC1: TBD
* Release: December 2, 2017

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

*  Add support of rcu_idle_{enter,exit}
   -  XEN-27
   -  Dario Faggioli

=== x86 ===

I am working on XEN-70, have already posted rfc. [1]

Also can you please add a xen-jira issue for the ITS ACPI support [2] v2 
patches,

which I have already sent and am working on next rev.

[1] https://www.mail-archive.com/xen-devel@lists.xen.org/msg110269.html
[2] https://www.mail-archive.com/xen-devel@lists.xen.org/msg111342.html




___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel



___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Yi Sun]

On 17-07-17 14:26:22, Julien Grall wrote:
Hi, Julien,

Please check latest versions of mine.

> *  Enable L2 Cache Allocation Technology (v8)
>   -  XEN-37
>   -  Yi Sun
>
v14:
https://lists.xenproject.org/archives/html/xen-devel/2017-07/msg01379.html
 
> *  Enable Memory Bandwidth Allocation (RFC)
>   -  XEN-48
>   -  Yi Sun
>
RFC v2:
https://lists.xenproject.org/archives/html/xen-devel/2017-07/msg01965.html

Thanks,
Sun Yi

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Xen 4.10 Development Update

[Daniel Kiper]

Hey Julien,

On Mon, Jul 17, 2017 at 02:26:22PM +0100, Julien Grall wrote:
> This email only tracks big items for xen.git tree. Please reply for items you
> woulk like to see in 4.10 so that people have an idea what is going on and
> prioritise accordingly.
>
> You're welcome to provide description and use cases of the feature you're
> working on.
>
> = Timeline =
>
> We now adopt a fixed cut-off date scheme. We will release twice a
> year. The upcoming 4.10 timeline are as followed:
>
> * Last posting date: September 15th, 2017
> * Hard code freeze: September 29th, 2017
> * RC1: TBD
> * Release: December 2, 2017
>
> Note that we don't have freeze exception scheme anymore. All patches
> that wish to go into 4.10 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
>
> *  Add support of rcu_idle_{enter,exit}
>   -  XEN-27
>   -  Dario Faggioli
>
> === x86 ===

Could you add the following project to the list?

*  Change xen.efi build and add SHIM_LOCK verification into efi_multiboot2()
  -  Daniel Kiper

This is probably more 4.11 material but let's have it on the 4.10 list too.
Who knows what may happen.

Thanks,

Daniel

___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel