xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org
Subject: Re: Xen 4.12 Development Update
Date: Fri, 9 Nov 2018 10:56:03 +0000	[thread overview]
Message-ID: <62458c5c-a6dc-f67d-ea93-a1bc7257b9ca@citrix.com> (raw)
In-Reply-To: <20181109101631.5729-1-jgross@suse.com>

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

  parent reply	other threads:[~2018-11-09 10:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 10:16 Xen 4.12 Development Update Juergen Gross
2018-11-09 10:40 ` Wei Liu
2018-11-09 10:53 ` Jan Beulich
2018-11-09 18:02   ` Dario Faggioli
2018-11-09 10:56 ` George Dunlap [this message]
2018-11-09 11:07   ` Juergen Gross
2018-11-09 11:32     ` George Dunlap
2018-11-09 11:44 ` Andrew Cooper
2018-11-09 12:05   ` Andrew Cooper
2018-11-09 14:50 ` Julien Grall
  -- strict thread matches above, loose matches on Subject: below --
2019-01-14 10:13 Juergen Gross
2019-01-14 10:52 ` Andrew Cooper
2019-01-14 15:22 ` Lars Kurth
2019-01-14 18:09   ` Stefano Stabellini
2018-12-17 14:14 Juergen Gross
2018-12-17 14:40 ` Razvan Cojocaru
2018-12-17 18:38   ` Tamas K Lengyel
2018-11-28 10:26 Juergen Gross
2018-11-28 10:36 ` Andrew Cooper
2018-11-28 15:30 ` Christopher Clark
2018-11-29 20:16 ` Volodymyr Babchuk
2018-11-30  5:34   ` Juergen Gross
2018-11-28 10:15 Juergen Gross
2018-11-28 10:19 ` Juergen Gross
2018-11-28 10:27 ` Paul Durrant
2018-10-08  8:44 Juergen Gross
2018-11-28  6:23 ` Chao Gao
2018-09-12  6:54 Juergen Gross
2018-09-12  8:20 ` Jan Beulich
2018-09-12  8:22   ` Paul Durrant
2018-10-02 19:06   ` Wei Liu
     [not found] ` <5B98CC5E02000078001E7A00@suse.com>
2018-09-12  8:30   ` Juergen Gross
2018-09-12  8:41     ` Jan Beulich
2018-07-27 16:19 Juergen Gross
2018-07-31 18:19 ` Rich Persaud

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=62458c5c-a6dc-f67d-ea93-a1bc7257b9ca@citrix.com \
    --to=george.dunlap@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).