From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: 4.2 TODO update
Date: Mon, 13 Feb 2012 11:11:14 -0800 [thread overview]
Message-ID: <CAP8mzPNoK+vvDUfz3Te5Xhj4JWk08aOUwTSjdieR+qDXHPMbjA@mail.gmail.com> (raw)
In-Reply-To: <1329128265.31256.24.camel@zakaz.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1499 bytes --]
On Mon, Feb 13, 2012 at 2:17 AM, Ian Campbell <Ian.Campbell@citrix.com>wrote:
>
> tools, nice to have:
>
> * Hotplug script stuff -- internal to libxl (I think, therefore I
> didn't put this under stable API above) but still good to have
> for 4.2? (Roger Pau Monet, patches posted)
> * Block script support -- follows on from hotplug script (Roger
> Pau Monet)
> * libyajl v2 support (Roger Pau Monet, DONE)
> * Configure/control paging via xl/libxl (Olaf Herring)
> * Upstream qemu feature patches:
> * Upstream qemu PCI passthrough support (Anthony Perard)
> * Upstream qemu save restore (Anthony Perard, Stefano
> Stabellini)
> * Nested-virtualisation (currently should be marked
> experimental,likely to release that way? Consider nested-svm
> separate to nested-vmx. Nested-svm is in better shape)
> * Initial xl support for Remus (memory checkpoint, blackholing)
> (Shriram, patches posted)
>
>
FYI, the network buffering module which was part of 2.6.32 pvops tree has
been accepted into upstream net-next tree. I have also posted patches for
the
userspace libnl code that talks to the qdiscs via netlink.
I am just waiting for the initial xl patches to go in, after which I could
take a stab
at adding network buffering support. Depending on whether Roger's hotplug
patches
go in or not, I could add some rudimentary disk replication support, time
permitting.
shriram
[-- Attachment #1.2: Type: text/html, Size: 1876 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-02-13 19:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 10:17 4.2 TODO update Ian Campbell
2012-02-13 10:24 ` Tim Deegan
2012-02-13 10:46 ` George Dunlap
2012-02-13 11:05 ` Fantu
2012-02-13 11:23 ` Ian Campbell
2012-02-13 11:50 ` Anthony PERARD
2012-02-13 11:56 ` Ian Campbell
2012-02-21 2:38 ` Michael A. Collins
2012-02-21 8:51 ` Ian Campbell
2012-02-13 11:29 ` Jan Beulich
2012-02-13 11:32 ` Ian Campbell
2012-02-13 12:04 ` Jan Beulich
2012-02-13 12:18 ` Stefano Stabellini
2012-02-14 14:56 ` Jan Beulich
2012-02-13 11:39 ` Anthony PERARD
2012-02-13 11:57 ` Stefano Stabellini
2012-02-13 19:11 ` Shriram Rajagopalan [this message]
2012-02-17 10:23 ` Ian Campbell
[not found] <mailman.3388.1329129411.1471.xen-devel@lists.xensource.com>
2012-02-14 14:58 ` Andres Lagar-Cavilla
2012-02-14 15:18 ` Olaf Hering
2012-02-14 16:47 ` Andres Lagar-Cavilla
2012-02-14 17:18 ` Olaf Hering
2012-02-14 17:34 ` Andres Lagar-Cavilla
2012-02-14 20:05 ` Tim Deegan
2012-02-15 16:22 ` Andres Lagar-Cavilla
2012-02-15 17:07 ` Tim Deegan
-- strict thread matches above, loose matches on Subject: below --
2012-02-20 15:52 Ian Campbell
[not found] <mailman.4065.1329753857.1471.xen-devel@lists.xensource.com>
2012-02-20 20:00 ` Andres Lagar-Cavilla
2012-03-12 12:11 Ian Campbell
2012-03-12 13:42 ` Ian Campbell
2012-03-12 13:51 ` Jan Beulich
2012-03-12 15:27 ` Ian Campbell
2012-03-12 13:55 ` Roger Pau Monné
2012-03-12 16:01 ` Stefano Stabellini
2012-03-13 8:57 ` Ian Campbell
2012-03-12 16:36 ` George Dunlap
2012-03-12 16:42 ` Ian Campbell
2012-03-13 10:50 ` George Dunlap
2012-03-14 16:48 ` Dario Faggioli
2012-03-14 16:51 ` 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=CAP8mzPNoK+vvDUfz3Te5Xhj4JWk08aOUwTSjdieR+qDXHPMbjA@mail.gmail.com \
--to=rshriram@cs.ubc.ca \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).