Re: trace_exec_tb(tb, pc) does not have cpu index

["Alex Bennée" <alex.bennee@linaro.org>]

Igor Lesik <lesikigor@meta.com> writes:

> Hi.
>
> I am wondering why trace events like trace_exec_tb(tb, pc) do not have
> cpu index, how to make sense of the trace in case of multiple vCPUs?
> I have changed it to trace_exec_tb(tb, pc, cpu->cpu_index) to read my
> trace, and now wondering should not it be there by default? Am I
> missing something?

Not necessarily but be aware trace_exec_tb won't catch every execution
of a TB without -d nochain anyway. There are other trace points/logging
methods you could use (-d cpu) which follow the executed PC more closely
although without the TB associated with it, although again needing
nochain for completeness.

It really depends on what your overall aim is? If you really want to
closely follow what a guest is doing then build an experiment using TCG
plugins where you can flexibly instrument and trace execution. If you
are debugging TB execution does the vCPU it runs on really matter?


>
> I am using "simple" trace backend.
>
> Thanks,
> Igor


-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro