From: "Steven Rostedt (VMware)" <rostedt@xxxxxxxxxxx> Use tracing the wake-up and kvm-exit events to find the task that is owned by the given CID. Also, do the same to find the mappings of threads and the guest vCPUs. Changes since v2: - Added the two patches together into a single series: https://lore.kernel.org/linux-trace-devel/20210506171400.7c00b731@xxxxxxxxxxxxxxxxxx/ https://lore.kernel.org/linux-trace-devel/20210507135615.033a6121@xxxxxxxxxxxxxxxxxx/ - Rewrote the change log for the first patch to explain the problem better. - Used some of the new APIs of libtracefs 1.2 to simplify the code - Still call read_qemu_gusts() but only if the CID is not supplied on the command line. Steven Rostedt (VMware) (2): trace-cmd: Find PID of host-guest task from tracing vsock connection trace-cmd: Trace timesync to find pids that map vCPUs tracecmd/include/trace-local.h | 2 + tracecmd/trace-record.c | 202 ++++++++++++++++++++++++++++- tracecmd/trace-vm.c | 227 ++++++++++++++++++++++++++++++++- 3 files changed, 429 insertions(+), 2 deletions(-) -- 2.29.2
|