From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] ocaml: xc bindings: use libxenctrl and libxenguest
Date: Fri, 10 Sep 2010 16:23:54 +0100 [thread overview]
Message-ID: <4C8A4D8A.7060703@eu.citrix.com> (raw)
In-Reply-To: <c2610f86abfb2c34a5a6.1284113454@cosworth.uk.xensource.com>
On 10/09/10 11:10, Ian Campbell wrote:
> # HG changeset patch
> # User Ian Campbell<ian.campbell@citrix.com>
> # Date 1284113402 -3600
> # Node ID c2610f86abfb2c34a5a653dea29d5518fb355628
> # Parent 8a710e0eb0881cad6156500bd4cedcebc7824a18
> ocaml: xc bindings: use libxenctrl and libxenguest
>
> Now that tools/libxc is licensed under LGPL I don't think there is any
> need for an LGPL reimplementation under tools/ocaml.
>
> For the most part the conversion to the up-to-date libxc API (xc_lib.c
> essentially implemented the same interface as an older libxc) was
> pretty automatic. There are some functions which appear to no longer
> exist in libxc which I therefore simply removed the bindings for and a
> small number of interfaces which had changed.
>
> Many of the functions bound by the stubs have no in-tree users (which
> I think is fine for a language binding) so I have no way to confirm
> correctness other than by eye. I was however able to confirm that
> oxenstored still worked.
>
I can't say, i'm particularly thrilled by this patch.
on one hand, it renders oxenstored runnable on netbsd for example and
merge libxc into one.
on the other hand, it's a pretty big change and done only "one-sidedly":
- lose the logging improvement over libxenctrl version.
- some bindings get lost, need to adapt all clients.
- introduce pthread functions in the ocaml stack, which as discussed in
the past, might be a dealkiller, but unfortunately very hard to test.
- almost completely not tested patch.
oxenstored won't be affected much by all this, since it's using only a
tiny part of xc, but i suspect it might be a big deal for XCP and such,
and thus i wonder if XCP is going to use this version of xc (which was
the goal when merging those libraries alongside oxenstored). it would
probably be easier to test this in XCP first, since there's a
comprehensive test suite there.
--
Vincent
next prev parent reply other threads:[~2010-09-10 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 10:10 [PATCH] ocaml: xc bindings: use libxenctrl and libxenguest Ian Campbell
2010-09-10 10:33 ` Ian Campbell
2010-09-10 15:53 ` Vincent Hanquez
2010-09-10 15:23 ` Vincent Hanquez [this message]
2010-09-10 16:48 ` Ian Campbell
2010-09-10 17:22 ` Ian Jackson
2010-09-14 10:26 ` Vincent Hanquez
2010-10-01 16:26 ` Stefano Stabellini
2010-10-01 16:28 ` 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=4C8A4D8A.7060703@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Ian.Campbell@eu.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 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.