Hi Lluis, On 01/27/2016 07:54 PM, Lluís Vilanova wrote: > There is this modified version I wrote [1], which precisely provides a plugin > infrastructure to attach callbacks into guest code events (a binary > instrumentation framework based on QEMU). At the time, the discussion resolved > that a full code instrumentation interface for plugins was too much code that > regular QEMU users & developers would not care about, easily leading to > bitrot. >
This is too bad but looking at the discussion back then the argumentation is reasonable since an instrumentation API would and should touch everything in QEMU. > Instead, the list resolved (AFAIU) that it would be better to mainstream > support > for guest code events, and make instrumentation an unofficial extension. I've > been (slowly) working to separate both pieces, making instrumentation a QEMU > patch that can be easily maintained out of tree. > > The last patch series I sent sets the final stone on the core infrastructure > for > the mainline part, just missing the patches I have queued to start adding > guest > code trace events. Can you give me the name of the series. > > So, I'd say that such support is on the list of current developments (at least > mine, specially now that I have a bit more time for it). But getting the core > infrastructure mainlined takes some time to ensure it makes sense and can be > easily maintained and be generally usefull to vanilla QEMU. > For us such a API would make a lot of sense and there is no benefit for us to do our own API. Would it make sense for you if we helped you? Cheers, Bastian
