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

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

On 27 Oct 2014, at 11:17, Thomas Leonard <talex5@xxxxxxxxx> wrote:
> Note that everything should (in future) compile with an unmodified
> Lwt. Pinning the tracing version of Lwt is what will trigger
> everything to recompile with profiling support. So, getting this
> upstream shouldn't block anything (and might indeed be difficult),
> although if upstream wants to add a flag for it that would be great
> too.
> This is a change to my previous plan of having Lwt depend on
> mirage-profiling. Now, mirage-profiling depends on Lwt. If you want to
> use any extended feature of Lwt you should go via profiling. e.g. in
> mirage-platform we have:
> let ports = Array.init nr_events (fun port -> {
>  counter = program_start;
>  c = Profile.named_condition ("after-chn-" ^ string_of_int port)
> })
> If Lwt.tracing is installed then Profile.named_condition is:
> let named_condition label =
>  Lwt_condition.create ~label ()
> Without, it will be:
> let named_condition _label = Lwt_condition.create ()

This also sounds like the right order, and permits other tracing
strategies in the future for Lwt.  Are you doing the mirage-platform
conditional compilation via optcomp?

MirageOS-devel mailing list



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