All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] perf intel-pt: Add support for emulated ptwrite
Date: Mon,  9 May 2022 18:23:57 +0300	[thread overview]
Message-ID: <20220509152400.376613-1-adrian.hunter@intel.com> (raw)

Hi

Here are 3 patches (on top of "perf intel-pt: Add link to the perf wiki's
Intel PT page") to add support for decoding emulated ptwrite i.e. for
hardware that does not have the ptwrite instruction.


Adrian Hunter (3):
      perf intel-pt: Add support for emulated ptwrite
      perf script: Print Intel ptwrite value as a string if it is ASCII
      perf scripts python: intel-pt-events.py: Print ptwrite value as a string if it is ASCII

 tools/perf/Documentation/perf-intel-pt.txt         | 88 +++++++++++++++++++
 tools/perf/builtin-script.c                        | 32 ++++++-
 tools/perf/scripts/python/intel-pt-events.py       |  8 +-
 .../perf/util/intel-pt-decoder/intel-pt-decoder.c  | 99 +++++++++++++++++++++-
 .../perf/util/intel-pt-decoder/intel-pt-decoder.h  |  1 +
 .../util/intel-pt-decoder/intel-pt-insn-decoder.c  |  1 +
 .../util/intel-pt-decoder/intel-pt-insn-decoder.h  |  1 +
 tools/perf/util/intel-pt.c                         | 37 +++++++-
 8 files changed, 261 insertions(+), 6 deletions(-)


Regards
Adrian

             reply	other threads:[~2022-05-09 15:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 15:23 Adrian Hunter [this message]
2022-05-09 15:23 ` [PATCH 1/3] perf intel-pt: Add support for emulated ptwrite Adrian Hunter
2022-05-09 15:23 ` [PATCH 2/3] perf script: Print Intel ptwrite value as a string if it is ASCII Adrian Hunter
2022-05-09 15:24 ` [PATCH 3/3] perf scripts python: intel-pt-events.py: Print " Adrian Hunter
2022-05-17 13:13 ` [PATCH 0/3] perf intel-pt: Add support for emulated ptwrite Adrian Hunter
2022-05-17 14:56   ` Arnaldo Carvalho de Melo

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=20220509152400.376613-1-adrian.hunter@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.