xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.4 development update: Code freezing point reached
Date: Tue, 19 Nov 2013 16:18:32 +0000	[thread overview]
Message-ID: <528B8F58.1030702@eu.citrix.com> (raw)
In-Reply-To: <20131118192252.GA2924@reaktio.net>

On 11/18/2013 07:22 PM, Pasi Kärkkäinen wrote:
> On Mon, Nov 18, 2013 at 06:19:46PM +0000, George Dunlap wrote:
>>
>> = Timeline =
>>
>> Here is our current timeline based on a 6-month release:
>>
>> * Feature freeze: 18 October 2013
>> * Code freezing point: 18 November 2013 <== WE ARE HERE
>> * First RC: 6 December 2013
>> * Release: 21 January 2014
>>
>> Last updated: 18 November 2016
>>
>
> 2016 :)
>
>
>>
>> == Backlog ==
>>
>>
>> === Big ticket items ===
>>
>
>   * PCI hole resize support hvmloader/qemu-traditional/qemu-upstream with PCI/GPU passthrough
>     http://lists.xen.org/archives/html/xen-devel/2013-05/msg02813.html
>     Where Stefano writes:
>
>     1) modify upstream QEMU to start the PCI hole at 0xe0000000, to match
>     qemu-xen-unstable in terms of configuration and not to introduce any
>     regressions. Do this for the Xen 4.3 release.
>
>     2) for Xen 4.4 rework the two patches above and improve
>     i440fx_update_pci_mem_hole: resizing the pci_hole subregion is not
>     enough, it also needs to be able to resize the system memory region
>     (xen.ram) to make room for the bigger pci_hole

Right -- I'll put it on my list; but given that it needs a new interface 
into qemu, and work hasn't even begun on that yet, I rather doubt it's 
going to make it for 4.4, unfortunately. :-(

  -George

  reply	other threads:[~2013-11-19 16:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 18:19 Xen 4.4 development update: Code freezing point reached George Dunlap
2013-11-18 18:52 ` Dario Faggioli
2013-11-18 19:22 ` Pasi Kärkkäinen
2013-11-19 16:18   ` George Dunlap [this message]
2013-11-19  0:59 ` Don Slutz
2013-11-19 17:46   ` George Dunlap
2013-11-19 10:50 ` Roger Pau Monné
2013-11-19 11:06   ` George Dunlap
2013-11-19 11:31     ` Roger Pau Monné
2013-11-19 14:00 ` Ian Campbell
2013-11-19 14:40 ` Konrad Rzeszutek Wilk
2013-11-19 14:54   ` Jan Beulich
2013-11-19 15:11     ` Konrad Rzeszutek Wilk
2013-11-19 17:52   ` George Dunlap
2013-11-19 19:40     ` Konrad Rzeszutek Wilk
2013-11-20  3:17   ` Zhenzhong Duan

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=528B8F58.1030702@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=pasik@iki.fi \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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).