Lluís Vilanova writes: > Bastian Koppelmann writes: >> Hi Lluis, >> On 01/27/2016 07:54 PM, Lluís Vilanova wrote: [...] >>> >>> 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? > Definitely. The instrumentation code needs some serious update to bring it > up-to-date with the latest QEMU, but adding generally useful guest code > tracing > events is something that can be easily pararellized. FYI, I've rebased my local queue and pushed it to the public repository [1]. Note that except for the head of the queue, patches are not tested (may not even compile), but it's a first step at seriously rebooting the project. I've also started splitting some of the series into separate branches to ease their development in parallel (devel-*). [1] https://projects.gso.ac.upc.edu/projects/qemu-dbi https://code.gso.ac.upc.edu/git/qemu-dbi PS: if you had a previous checkout, you might need to get it again (or do some tedious checkout+rm+merge+checkout sequence), since I'm developing all these series using stgit (which rewrites the story). Cheers, Lluis
