xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@entel.upc.edu>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xen 4.2 TODO List Update
Date: Wed, 25 Jan 2012 15:33:02 +0100	[thread overview]
Message-ID: <CAPLaKK49YTYQzMtSnphxnjbic0Da++SPROKBGFEQj1JNwSp_Fg@mail.gmail.com> (raw)
In-Reply-To: <1327324745.24561.124.camel@zakaz.uk.xensource.com>

2012/1/23 Ian Campbell <Ian.Campbell@citrix.com>:
> Newly updated list follows. Please send me corrections (especially
> "done"). I've stopped CCing everyone, since I guess it is mostly spam to
> the majority.
>
> hypervisor, blockers:
>
>      * round-up of the closing of the security hole in MSI-X
>        passthrough (uniformly - i.e. even for Dom0 - disallowing write
>        access to MSI-X table pages). (Jan Beulich -- more fixes
>        required than first thought, patches posted)
>      * domctls / sysctls set up to modify scheduler parameters, like
>        the credit1 timeslice and schedule rate. (George Dunlap)
>      * get the interface changes for sharing/paging/mem-events done and
>        dusted so that 4.2 is a stable API that we hold to. (Tim Deegan,
>        Andres Lagar-Cavilla et al)
>              * mem event ring management posted, seems close to going
>                in.
>              * sharing patches posted
>
> tools, blockers:
>
>      * libxl stable API -- we would like 4.2 to define a stable API
>        which downstream's can start to rely on not changing. Aspects of
>        this are:
>              * event handling (Ian Jackson, posted several rounds,
>                nearing completion?)
>              * drop libxl_device_model_info (move bits to build_info or
>                elsewhere as appropriate) (Ian Campbell, first RFC sent)
>              * add libxl_defbool and generally try and arrange that
>                memset(foo,0,...) requests the defaults (Ian Campbell,
>                first RFC sent)
>              * topologyinfo datastructure should be a list of tuples,
>                not a tuple of lists. (nobody currently looking at this,
>                not 100% sure this makes sense, could possibly defer and
>                change after 4.2 in a compatible way)
>      * xl to use json for machine readable output instead of sexp by
>        default (Ian Campbell to revisit existing patch)
>      * xl support for vcpu pinning (Dario Faggioli)
>      * xl feature parity with xend wrt driver domain support (George
>        Dunlap)
>      * Integrate qemu+seabios upstream into the build (patches
>        reposted, pending). No change in default qemu for 4.2.
>      * More formally deprecate xm/xend. Manpage patches already in
>        tree. Needs release noting and communication around -rc1 to
>        remind people to test xl.
>
> hypervisor, nice to have:
>
>      * solid implementation of sharing/paging/mem-events (using work
>        queues) (Tim Deegan, Olaf Herring et al)
>      * A long standing issue is a fully synchronized p2m (locking
>        lookups) (Andres Lagar-Cavilla)
>      * NUMA improvement: domain affinity consistent with cpupool
>        membership (Dario Faggioli, Jeurgen Gross -- patch posted)
>
> 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 was looking at this but its looking
>        like a big can-o-worms. (discussion on-going)
>      * Block script support -- follows on from hotplug script (Roger
>        Pau Monet)
>      * libyajl v2 support (patch posted by Roger Pau Monet, blocked on
>        autoconf?)
>      * 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)
>      * 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)


Just a random thought, but I find it quite annoying to need latex to
compile the documentation. I think it will be wise to create a new
Makefile target, like man-pages and install-man-pages to allow the
user to build and install man pages only (or don't abort docs build if
latex is not found). Personally I don't have latex on my server, and I
don't want to install it, but I would like to have the man pages when
building Xen from source.

> Tools, need to decide if pre- or post-4.2 feature:
>
>      * Autoconf (Roger Pau Monet posted a patch)
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2012-01-25 14:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 13:19 Xen 4.2 TODO List Update Ian Campbell
2012-01-23 16:07 ` Ian Campbell
2012-01-23 18:22 ` Dario Faggioli
2012-01-24 14:31 ` Juergen Gross
2012-01-24 19:28   ` Shriram Rajagopalan
2012-01-25 14:33 ` Roger Pau Monné [this message]
2012-01-25 14:41   ` Ian Campbell
2012-01-25 14:49     ` Roger Pau Monné
2012-01-25 14:57       ` Keir Fraser
2012-01-25 15:41         ` Ian Campbell
2012-01-25 14:59       ` Ian Campbell
2012-01-25 15:03         ` Roger Pau Monné
2012-01-25 15:40           ` Ian Campbell
2012-01-25 15:55             ` Keir Fraser
2012-01-26 14:57               ` Roger Pau Monné
  -- strict thread matches above, loose matches on Subject: below --
2012-01-31 11:51 Ian Campbell
2012-01-17 10:00 Ian Campbell
2012-01-17 10:04 ` Roger Pau Monné
2012-01-17 10:08 ` Olaf Hering
2012-01-17 10:53 ` Olaf Hering
2012-01-17 11:02   ` 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=CAPLaKK49YTYQzMtSnphxnjbic0Da++SPROKBGFEQj1JNwSp_Fg@mail.gmail.com \
    --to=roger.pau@entel.upc.edu \
    --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).