On 15 September 2017 at 14:39, Lluís Vilanova <vilan...@ac.upc.edu> wrote: > Peter Maydell writes: >> This looks like it's exposing too much implementation detail. >> We should just provide an API for "hook to be called for >> memory writes" which gets all the information when it >> is called. I don't think we should expose any kind of >> "this hook is called at translation time" at all. > > The differentiation between translation-time and execution-time is key to > perform certain analysis efficiently.
It's also exposing internal QEMU implementation detail. What if in future we decide to switch from our current setup to always interpreting guest instructions as a first pass with JITting done only in the background for hot code? Sticking to instrumentation events that correspond exactly to guest execution events means they won't break or expose internals. thanks -- PMM
