From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.4 development update -- RFC for feature freeze timeline
Date: Fri, 27 Sep 2013 10:37:26 +0100 [thread overview]
Message-ID: <524551D6.3050806@citrix.com> (raw)
In-Reply-To: <5245520902000078000F7458@nat28.tlf.novell.com>
On 27/09/13 08:38, Jan Beulich wrote:
>>>> On 26.09.13 at 18:47, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
>> * Event channel scalability
>
> I don't recall there having been significant change requests to the
> last posting - David, what's your estimation here?
The hypervisor and toolstack changes are now done. There's one
remaining issue with the Linux side.
Should be easily done before Oct 18.
I can repost the Xen series now if people would prefer an earlier review.
David
next prev parent reply other threads:[~2013-09-27 9:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 16:47 Xen 4.4 development update -- RFC for feature freeze timeline George Dunlap
2013-09-26 17:24 ` Dario Faggioli
2013-09-27 6:21 ` Elena Ufimtseva
2013-09-27 7:38 ` Jan Beulich
2013-09-27 9:37 ` David Vrabel [this message]
2013-09-27 9:51 ` Jan Beulich
2013-09-27 7:41 ` Jan Beulich
2013-10-04 17:36 ` George Dunlap
2013-09-27 10:21 ` Stefano Stabellini
2013-10-08 18:05 ` Xen 4.4 development update, qemu pci hole start address Pasi Kärkkäinen
2013-10-08 18:13 ` Pasi Kärkkäinen
2013-10-09 10:39 ` George Dunlap
2013-11-11 18:17 ` Pasi Kärkkäinen
2013-09-27 11:52 Xen 4.4 development update -- RFC for feature freeze timeline Boris Ostrovsky
2013-10-04 15:59 ` George Dunlap
2013-10-07 4:59 유재용
2013-10-07 6:55 ` Jan Beulich
2013-10-07 9:53 ` George Dunlap
2013-10-07 10:45 Jaeyong Yoo
2013-10-07 10:49 유재용
2013-10-07 11:25 ` Ian Campbell
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=524551D6.3050806@citrix.com \
--to=david.vrabel@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.