summaryrefslogtreecommitdiff
path: root/drivers/isdn/hardware
diff options
context:
space:
mode:
authorAdrian Hunter <adrian.hunter@intel.com>2022-07-11 12:31:53 +0300
committerArnaldo Carvalho de Melo <acme@redhat.com>2022-07-20 17:07:58 +0300
commitb47bb18661eaed30790d70b7563a5220b3c59594 (patch)
tree457ad457fa1a80154ebb02f1ff0e3806ae4a70a5 /drivers/isdn/hardware
parentc1fd5b7d8aed8104d5189c3d55545d67f9149bb6 (diff)
downloadlinux-b47bb18661eaed30790d70b7563a5220b3c59594.tar.xz
perf tools: Add machine_pid and vcpu to id_index
When injecting events from a guest perf.data file, the events will have separate sample ID numbers. These ID numbers can then be used to determine which machine an event belongs to. To facilitate that, add machine_pid and vcpu to id_index records. For backward compatibility, these are added at the end of the record, and the length of the record is used to determine if they are present or not. Note, this is needed because the events from a guest perf.data file contain the pid/tid of the process running at that time inside the VM not the pid/tid of the (QEMU) hypervisor thread. So a way is needed to relate guest events back to the guest machine and VCPU, and using sample ID numbers for that is relatively simple and convenient. Signed-off-by: Adrian Hunter <adrian.hunter@intel.com> Cc: Andi Kleen <ak@linux.intel.com> Cc: Ian Rogers <irogers@google.com> Cc: Jiri Olsa <jolsa@kernel.org> Cc: Namhyung Kim <namhyung@kernel.org> Cc: kvm@vger.kernel.org Link: https://lore.kernel.org/r/20220711093218.10967-11-adrian.hunter@intel.com Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Diffstat (limited to 'drivers/isdn/hardware')
0 files changed, 0 insertions, 0 deletions