[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] Mirage tracing

On 9 Oct 2014, at 12:25, Thomas Leonard <talex5@xxxxxxxxx> wrote:

> On 9 October 2014 11:25, Thomas Gazagnaire <thomas@xxxxxxxxxxxxxx> wrote:
>>>> I'm currently working on improving the profiling support in Mirage.
>>>> Previously [1], I was just graphing stats in libreoffice and looking
>>>> at call traces, but I've been thinking about how to get more useful
>>>> data.
>>>> Tracing individual functions was too fine-grained, I think, and failed
>>>> to follow Lwt threads, so I intrumented Lwt to record when threads are
>>>> created and resolved, and the interactions between them. Graphing the
>>>> results looks like this:
>>>> http://test.roscidus.com/static/block-read-mirage-x86.png
>>>> ( trace file: http://test.roscidus.com/static/log-x86.sexp )
>> That's pretty cool! That would be even cooler to have a HTML/CSS/javascript 
>> output on a "debug" port for any unikernel :-)
> It's using cairo for rendering, so producing png or svg output should
> be easy. My javascript skills aren't up to making it zoom smoothly in
> a browser though...

Regarding rendering, Daniel Buenzli's Vz library does have a js_of_ocaml
backend, so this may be a good place to get started on a browser backend
without the trouble of learning HTML/CSS:


I'll send an update on Conduit soon, but Dave Scott has added sufficient
Cohttp support that we could expose a Cohttp/Vchan from a unikernel and
access it via Linux userspace.  In other words: you can use Chrome or Firefox
to access the debugging port without going through TCP, which is pretty
cool :-)

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.