All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Osterloh <osterlohm@ainfosec.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Current LibXL Status
Date: Wed, 18 Nov 2015 18:32:28 +0000	[thread overview]
Message-ID: <564CC43B.1000904@ainfosec.com> (raw)

Hello All,

I am currently working on the OpenXT project [1]. My work is currently 
focused on creating a shim layer between XenMgr [2] (written in Haskell) 
and LibXL. Goal is to replace the current XenOps/XenVM [3] (written in 
OCaml).

I wanted to inquire about the current state of LibXL and in particular 
if there are any issues with using it in long-running processes.

Any feedback would be much appreciated.

Regards,

Martin Osterloh

[1]https://github.com/OpenXT
[2]https://github.com/OpenXT/manager
[3]https://github.com/OpenXT/toolstack

             reply	other threads:[~2015-11-18 18:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 18:32 Martin Osterloh [this message]
2015-11-19  9:20 ` Current LibXL Status Ian Campbell
2015-11-19 10:23   ` George Dunlap
2015-11-19 10:55   ` Andrew Cooper
2015-11-19 11:23     ` Ian Campbell
2015-11-19 11:30       ` Processed: " xen
2015-11-19 11:33       ` Andrew Cooper
2015-11-19 11:48         ` Ian Campbell
2015-11-19 11:55           ` Ian Campbell
2015-11-19 12:16             ` Ian Campbell
2015-11-20  0:30               ` Yang Hongyang
2016-02-18 17:09               ` George Dunlap
2016-02-18 17:19                 ` Ian Jackson
2016-02-18 17:26                   ` Ian Campbell
2016-02-18 17:40                     ` George Dunlap
2016-02-18 17:24                 ` Ian Campbell
2016-02-18 18:30           ` Ian Jackson
2015-11-19 15:34       ` George Dunlap
2016-02-18 17:26       ` George Dunlap
2016-02-18 17:39         ` Ian Campbell
2016-02-18 17:47           ` George Dunlap
2016-02-18 17:50           ` Ian Campbell
2016-02-18 18:15     ` libxl and malloc failure (Re: Current LibXL Status) Ian Jackson
2016-02-19 10:52       ` Ian Campbell
2016-02-19 11:00         ` Processed: " xen
2016-02-22 16:48         ` Ian Jackson

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=564CC43B.1000904@ainfosec.com \
    --to=osterlohm@ainfosec.com \
    --cc=xen-devel@lists.xen.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.