From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Ian Rogers <irogers@google.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] perf record: Preparation for sideband injection
Date: Fri, 10 Jun 2022 14:33:11 +0300 [thread overview]
Message-ID: <20220610113316.6682-1-adrian.hunter@intel.com> (raw)
Hi
Here are some small patches in preparation for "sideband injection".
I hope to run perf record in a virtual machine to capture sideband events
while simulataneously running perf record with Intel PT on the host, and
then subsequently inject the sideband events from the guest perf.data file
into the host perf.data file, so that decoding can decode the Intel PT
trace for the periods when the guest is running user space (kernel space
is already decodable).
The patches are changes I have found so far that will be needed.
Adrian Hunter (5):
perf record: Always get text_poke events with --kcore option
perf record: Always record id index
perf record: Add new option to sample identifier
perf record: Add finished init event
perf script: Add some missing event dumps
tools/lib/perf/include/perf/event.h | 1 +
tools/perf/Documentation/perf-record.txt | 3 +++
tools/perf/builtin-inject.c | 1 +
tools/perf/builtin-record.c | 44 +++++++++++++++++++++++++++-----
tools/perf/builtin-script.c | 6 +++++
tools/perf/util/event.c | 1 +
tools/perf/util/header.c | 3 +++
tools/perf/util/record.c | 2 +-
tools/perf/util/record.h | 1 +
tools/perf/util/session.c | 4 +++
tools/perf/util/synthetic-events.c | 7 +++--
tools/perf/util/tool.h | 3 ++-
12 files changed, 65 insertions(+), 11 deletions(-)
Regards
Adrian
next reply other threads:[~2022-06-10 11:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 11:33 Adrian Hunter [this message]
2022-06-10 11:33 ` [PATCH 1/5] perf record: Always get text_poke events with --kcore option Adrian Hunter
2022-06-10 11:33 ` [PATCH 2/5] perf record: Always record id index Adrian Hunter
2022-06-10 11:33 ` [PATCH 3/5] perf record: Add new option to sample identifier Adrian Hunter
2022-06-14 14:53 ` Ian Rogers
2022-06-15 5:25 ` [PATCH V2 " Adrian Hunter
2022-06-10 11:33 ` [PATCH 4/5] perf record: Add finished init event Adrian Hunter
2022-06-23 13:41 ` Arnaldo Carvalho de Melo
2022-06-23 13:46 ` Arnaldo Carvalho de Melo
2022-06-23 13:55 ` Arnaldo Carvalho de Melo
2022-06-23 18:41 ` Adrian Hunter
2022-06-10 11:33 ` [PATCH 5/5] perf script: Add some missing event dumps Adrian Hunter
2022-06-14 14:55 ` [PATCH 0/5] perf record: Preparation for sideband injection Ian Rogers
2022-06-23 9:32 ` 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=20220610113316.6682-1-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@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