On 7 June 2017 at 16:45, Lluís Vilanova <vilan...@ac.upc.edu> wrote: > This speed comes at the cost of exposing TCG operations to the instrumentation > library (i.e., the library can inject TCG code; AFAIR, calling out into a > function in the instrumentation library is slower than PIN).
Mmm, that's awkward. I'm not sure I'd really like to allow arbitrary user instrumentation to inject TCG code: it's exposing our rather changeable internals to the user, and it's a more complicated interface to understand. For user-facing API (as opposed to instrumentation interfaces within QEMU which we use to implement something more simplified to present to the user) I would favour a clean and straightforward API over pure speed. thanks -- PMM
