Re: [MirageOS-devel] Tracing and profiling blog post

[Thomas Leonard <talex5@xxxxxxxxx>]

On 28 October 2014 22:36, Daniel BÃnzli <daniel.buenzli@xxxxxxxxxxxx> wrote:
>
> Le mardi, 28 octobre 2014 Ã 23:21, Anil Madhavapeddy a Ãcrit :
>
>> Assemblage is still undergoing 'rapid iteration', so I'd suggest
>> switching to OASIS until we have a more stable version. ThomasG or
>> Daniel Buenzli can correct me if that's not accurate.
>
> That's accurate. If we agree with Thomas on the PR I'm going to make next 
> week, the current API completely changes and assemble.ml files will need 
> rewriting. We need time to design a great system and it's better if we don't 
> encumber ourselves with users at the moment.

OK, done (thanks to Thomas for some OPAM help!). I think the main
thing now is to agree the API for libraries to record tracing events.

Here's what I have so far:

https://github.com/talex5/mirage-profile/blob/new-api/lib/trace_stubs.mli
https://github.com/talex5/mirage-profile/blob/new-api/lib/counter.mli

There's not much here, but it would be good to keep this API stable as
pretty much all mirage libraries will be using it.

The API for controlling the tracing, dumping out events, etc is much
less critical and can be changed later, as it only matters to the
developer profiling their unikernel.

Comments welcome!


-- 
Dr Thomas Leonard        http://0install.net/
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel