From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH 0/2] perf intel-pt: Small updates
Date: Mon, 20 Mar 2023 20:35:15 +0200 [thread overview]
Message-ID: <20230320183517.15099-1-adrian.hunter@intel.com> (raw)
Hi
Here are 2 small updates for Intel PT.
The first is just a couple of new event type names.
The second is a small change to Intel PT as it relates to
Intel FRED. The patch is standalone but, for anyone
interested, you can search LKML for FRED to find out more
about Intel FRED implementation.
Adrian Hunter (2):
perf intel-pt: Add event type names UINTR and UIRET
perf intel-pt: Add support for new branch instructions ERETS and ERETU
tools/perf/arch/x86/tests/insn-x86.c | 4 ++++
tools/perf/builtin-script.c | 2 +-
.../perf/util/intel-pt-decoder/intel-pt-insn-decoder.c | 18 ++++++++++++++++++
.../perf/util/intel-pt-decoder/intel-pt-insn-decoder.h | 2 ++
4 files changed, 25 insertions(+), 1 deletion(-)
Regards
Adrian
next reply other threads:[~2023-03-20 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 18:35 Adrian Hunter [this message]
2023-03-20 18:35 ` [PATCH 1/2] perf intel-pt: Add event type names UINTR and UIRET Adrian Hunter
2023-03-20 18:35 ` [PATCH 2/2] perf intel-pt: Add support for new branch instructions ERETS and ERETU Adrian Hunter
2023-03-20 18:40 ` [PATCH 0/2] perf intel-pt: Small updates Ian Rogers
2023-03-20 22:25 ` 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=20230320183517.15099-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=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).