On 7 February 2014 14:49, Richard Henderson <r...@twiddle.net> wrote: > On 02/06/2014 11:26 AM, Lluís Vilanova wrote: >>> > At which point, option 2 would be the best bet, I think. >> Right. For the 3rd option I was also thinking about having per-vCPU tracing >> states (in the case of guest events), so that you can trace separate events >> depending on the vCPU. >> >> Which reminds me, I should add a vCPU pointer to the "guest_vmem" event, >> since >> otherwise you cannot differentiate accesses among different vCPUs. > > The TB cache is shared, so you won't be able to do option 3 for different > events for different cpus. You could only do option 1 for that
I have a vague plan in the back of my mind that we should make the TB cache be per-CPU, as a step towards better handling of multithreaded linux-user guest binaries and also heterogenous multiple CPU support... thanks -- PMM
