From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>, Leo Yan <leo.yan@linaro.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
kvm@vger.kernel.org
Subject: [PATCH 0/6] perf intel-pt: Add support for tracing KVM test programs
Date: Fri, 13 May 2022 12:02:31 +0300 [thread overview]
Message-ID: <20220513090237.10444-1-adrian.hunter@intel.com> (raw)
Hi
A common case for KVM test programs is that the guest object code can be
found in the hypervisor process (i.e. the test program running on the
host). Add support for that.
For some more details refer the 3rd patch "perf tools: Add guest_code
support"
For an example, see the last patch "perf intel-pt: Add guest_code support"
For more information about Perf tools support for Intel® Processor Trace
refer:
https://perf.wiki.kernel.org/index.php/Perf_tools_support_for_Intel%C2%AE_Processor_Trace
Adrian Hunter (6):
perf tools: Add machine to machines back pointer
perf tools: Factor out thread__set_guest_comm()
perf tools: Add guest_code support
perf script: Add guest_code support
perf kvm report: Add guest_code support
perf intel-pt: Add guest_code support
tools/perf/Documentation/perf-intel-pt.txt | 67 ++++++++++++++++++++++++
tools/perf/Documentation/perf-kvm.txt | 3 ++
tools/perf/Documentation/perf-script.txt | 4 ++
tools/perf/builtin-kvm.c | 2 +
tools/perf/builtin-script.c | 5 +-
tools/perf/util/event.c | 7 ++-
tools/perf/util/intel-pt.c | 20 ++++++-
tools/perf/util/machine.c | 84 ++++++++++++++++++++++++++++--
tools/perf/util/machine.h | 4 ++
tools/perf/util/session.c | 7 +++
tools/perf/util/symbol_conf.h | 3 +-
11 files changed, 197 insertions(+), 9 deletions(-)
Regards
Adrian
next reply other threads:[~2022-05-13 9:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 9:02 Adrian Hunter [this message]
2022-05-13 9:02 ` [PATCH 1/6] perf tools: Add machine to machines back pointer Adrian Hunter
2022-05-13 9:02 ` [PATCH 2/6] perf tools: Factor out thread__set_guest_comm() Adrian Hunter
2022-05-13 9:02 ` [PATCH 3/6] perf tools: Add guest_code support Adrian Hunter
2022-05-17 3:13 ` Namhyung Kim
2022-05-17 4:54 ` Adrian Hunter
2022-05-13 9:02 ` [PATCH 4/6] perf script: " Adrian Hunter
2022-05-13 9:02 ` [PATCH 5/6] perf kvm report: " Adrian Hunter
2022-05-13 9:02 ` [PATCH 6/6] perf intel-pt: " Adrian Hunter
2022-05-13 14:46 ` Andi Kleen
2022-05-13 15:14 ` Adrian Hunter
2022-05-13 18:13 ` Andi Kleen
2022-05-15 7:27 ` Adrian Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220513090237.10444-1-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).