xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org
Cc: jgross@suse.com, luwei.kang@intel.com, wl@xen.org,
	konrad.wilk@oracle.com, andrew.cooper3@citrix.com,
	marmarek@invisiblethingslab.com, dfaggioli@suse.com,
	paul.durrant@citrix.com, JBeulich@suse.com, puwen@hygon.cn,
	Volodymyr_Babchuk@epam.com, chao.gao@intel.com
Subject: [Xen-devel] [ANNOUNCE] Xen 4.13 Development Update
Date: Thu,  1 Aug 2019 18:00:48 +0200	[thread overview]
Message-ID: <20190801160048.11031-1-jgross@suse.com> (raw)

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

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

= Timeline =

We now adopt a fixed cut-off date scheme. We will release about every 8 months.
The upcoming 4.13 timeline are as followed:

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

Note that we don't have freeze exception scheme anymore. All patches
that wish to go into 4.13 must be posted initially no later than the
last posting date and finally no later than the hard code freeze. All
patches posted after that date will be automatically queued into next
release.

RCs will be arranged immediately after freeze.

We recently introduced a jira instance to track all the tasks (not only big)
for the project. See: https://xenproject.atlassian.net/projects/XEN/issues.

Some of the tasks tracked by this e-mail also have a corresponding jira task
referred by XEN-N.

I have started to include the version number of series associated to each
feature. Can each owner send an update on the version number if the series
was posted upstream?

= Projects =

== Hypervisor == 

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

*  Improvements to domain creation (v2)
  -  Andrew Cooper

*  Core aware scheduling (RFC v1)
  -  Dario Faggioli

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

*  Core scheduling (v1)
  -  Juergen Gross

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

=== x86 === 

*  PV-IOMMU (v7)
  -  Paul Durrant

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

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

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

*  Improve late microcode loading (v8)
  -  Chao Gao

*  Fixes to #DB injection
  -  Andrew Cooper

*  CPUID/MSR Xen/toolstack improvements
  -  Andrew Cooper

*  Improvements to domain_crash()
  -  Andrew Cooper

*  EIBRS
  -  Andrew Cooper

=== ARM === 

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

== Completed == 

*  Drop tmem
  -  Wei Liu

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

*  hypervisor x86 instruction emulator additions for AVX512
  -  Jan Beulich

*  x2APIC support for AMD
  -  Jan Beulich


Juergen Gross

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

             reply	other threads:[~2019-08-01 16:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 16:00 Juergen Gross [this message]
2019-08-01 16:47 ` [Xen-devel] [ANNOUNCE] Xen 4.13 Development Update Andrew Cooper
2019-08-02  8:50   ` Wei Liu
2019-08-01 18:11 ` Roman Shaposhnik
2019-08-02  9:04   ` Roger Pau Monné
2019-08-02  9:57 ` Dario Faggioli
2019-08-02 15:52 ` Anthony PERARD
2019-08-02 17:07   ` Oleksandr
2019-08-12 10:02 ` Paul Durrant
  -- strict thread matches above, loose matches on Subject: below --
2019-09-28  5:09 Juergen Gross
2019-09-28 14:07 ` Steven Haigh
2019-09-06  7:40 Juergen Gross
2019-09-06 16:13 ` Andrew Cooper
2019-09-06 16:32 ` Konrad Rzeszutek Wilk
2019-09-09  7:52 ` Paul Durrant
2019-09-12  5:46 ` Chao Gao
2019-09-12  6:10 ` Roman Shaposhnik
2019-09-12  6:36   ` Juergen Gross
2019-09-13 16:19     ` Oleksandr
2019-07-01 11:35 Juergen Gross
2019-07-01 11:42 ` Jan Beulich
2019-07-01 12:09   ` Juergen Gross
2019-07-01 17:24 ` Volodymyr Babchuk
2019-05-28 10:54 Juergen Gross
2019-05-28 10:54 ` [Xen-devel] " Juergen Gross
2019-05-28 13:44 ` Tamas K Lengyel
2019-05-28 13:44   ` [Xen-devel] " Tamas K Lengyel
2019-05-28 23:07   ` Andrew Cooper
2019-05-28 23:07     ` [Xen-devel] " Andrew Cooper

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=20190801160048.11031-1-jgross@suse.com \
    --to=jgross@suse.com \
    --cc=JBeulich@suse.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=chao.gao@intel.com \
    --cc=dfaggioli@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=luwei.kang@intel.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=paul.durrant@citrix.com \
    --cc=puwen@hygon.cn \
    --cc=wl@xen.org \
    --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).