Re: [Xen-devel] Xen 4.2 TODO List Update

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2012-01-25 at 14:49 +0000, Roger Pau Monnà wrote:
> 2012/1/25 Ian Campbell <Ian.Campbell@xxxxxxxxxx>:
> > On Wed, 2012-01-25 at 14:33 +0000, Roger Pau Monnà wrote:
> >> 2012/1/23 Ian Campbell <Ian.Campbell@xxxxxxxxxx>:
> >> > 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.
> >
> > "make -C docs man-pages" will do what you want.
> 
> Thanks, I've already done this to build them on my system, but I think
> we should provide some easy way for users without latex to build and
> install the man pages.

It's hard to get much easier, but...

> > I must admit I thought latex was optional and that "make docs" would
> > simply skip those docs if it wasn't installed -- that's what the "if
> > which $(TOOL)" construct used in there is (supposed to be) doing.
> 
> If latex is not found, the compilation is aborted:
> 
> # make docs
> sh ./docs/check_pkgs && make -C docs install || true
> =================================================
> =================================================
> = WARNING: Package 'latex' is required
> =          to build Xen documentation
> =================================================
> =================================================
> 
> I think make docs should just skip latex if not found.

Looks like it is simply the check which is too strict. AFAICT the actual
docs build already skips those docs if you don't have Latex. You can
test this with "make -C docs" which is basically the same as "make docs"
but without the checks.

Ian.



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