xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Juergen Gross' <jgross@suse.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.11 Development Update
Date: Fri, 5 Jan 2018 10:29:09 +0000	[thread overview]
Message-ID: <12f4252e4e784a27b7df36bf4d3afbe0@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20180105091638.4500-1-jgross@suse.com>

> -----Original Message-----
> From: Juergen Gross [mailto:jgross@suse.com]
> Sent: 05 January 2018 09:17
> To: xen-devel@lists.xenproject.org
> Cc: jgross@suse.com
> Subject: Xen 4.11 Development Update
> 
> This email only tracks big items for xen.git tree. Please reply for items you
> would like to see in 4.11 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.11 timeline are as followed:
> 
> * Last posting date: March 16th, 2018
> * Hard code freeze: March 30th, 2018
> * RC1: TBD
> * Release: June 1st, 2018
> 
> Note that we don't have freeze exception scheme anymore. All patches
> that wish to go into 4.11 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 ===
> 
> *  Enable Memory Bandwidth Allocation in Xen (v10)
>   -  XEN-48
>   -  Yi Sun
> 
> *  guest resource mapping (v17)
>   -  Paul Durrant
> 

Could you also add PV-IOMMU here? I do have some preliminary patches and have successfully tested a dom0 with a 1:1 GFN:BFN mapping set up using the new hypercalls, so I expect to post something in time for 4.11.

Thanks,

  Paul

> *  vNVDIMM support for HVM guest (RFC v4)
>   -  XEN-45
>   -  Haozhong Zhang
> 
> *  SMMUv3 driver (RFC v4)
>   -  Sameer Goel
> 
> == Grub2 ==
> 
> *  Support PVH guest boot (v1)
>   -  Juergen Gross
> 
> 

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

  parent reply	other threads:[~2018-01-05 10:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05  9:16 Xen 4.11 Development Update Juergen Gross
2018-01-05  9:32 ` Jan Beulich
2018-01-05  9:56 ` Manish Jaggi
     [not found] ` <5A4F542E020000780019B49A@suse.com>
2018-01-05  9:57   ` Juergen Gross
2018-01-05 10:24     ` Jan Beulich
2018-01-05 10:29 ` Paul Durrant [this message]
2018-01-08 12:29 ` Wei Liu
2018-01-08 12:35   ` Juergen Gross
  -- strict thread matches above, loose matches on Subject: below --
2018-01-31  6:57 Juergen Gross
2018-01-31  9:17 ` Roger Pau Monné
2018-01-31  9:18 ` Ross Lagerwall
2018-01-31  9:57 ` Jan Beulich
2018-02-01  1:39   ` Yi Sun
2018-01-31 11:24 ` Wei Liu
2018-02-01 14:04 ` Andrew Cooper
2018-02-28  8:23 Juergen Gross
2018-03-09 17:50 ` Dario Faggioli
2018-03-19  5:49 Juergen Gross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=12f4252e4e784a27b7df36bf4d3afbe0@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=jgross@suse.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).