From: Ravi Bangoria <ravi.bangoria@amd.com>
To: <peterz@infradead.org>
Cc: <ravi.bangoria@amd.com>, <eranian@google.com>, <acme@kernel.org>,
<mark.rutland@arm.com>, <jolsa@kernel.org>, <namhyung@kernel.org>,
<irogers@google.com>, <bp@alien8.de>, <x86@kernel.org>,
<linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <sandipan.das@amd.com>,
<ananth.narayan@amd.com>, <santosh.shukla@amd.com>
Subject: [PATCH 0/2] perf/ibs: Fix interface via core pmu events
Date: Thu, 2 Mar 2023 14:51:07 +0530 [thread overview]
Message-ID: <20230302092109.367-1-ravi.bangoria@amd.com> (raw)
IBS used to allow event creation via core pmu events with precise_ip
attribute set, but it's broken since late 2019. 1st patch fixes the
issue and 2nd patch adds simple perf test for the same.
Ravi Bangoria (2):
perf/ibs: Fix interface via core pmu events
perf test: Add selftest to test IBS invocation via core pmu events
arch/x86/events/amd/core.c | 5 +++
arch/x86/events/core.c | 2 +
arch/x86/events/perf_event.h | 3 ++
include/linux/perf_event.h | 1 +
kernel/events/core.c | 11 +++--
tools/perf/tests/Build | 1 +
tools/perf/tests/builtin-test.c | 1 +
tools/perf/tests/ibs-via-core-pmu.c | 70 +++++++++++++++++++++++++++++
tools/perf/tests/tests.h | 1 +
9 files changed, 92 insertions(+), 3 deletions(-)
create mode 100644 tools/perf/tests/ibs-via-core-pmu.c
--
2.39.2
next reply other threads:[~2023-03-02 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 9:21 Ravi Bangoria [this message]
2023-03-02 9:21 ` [PATCH 1/2] perf/ibs: Fix interface via core pmu events Ravi Bangoria
2023-03-02 22:10 ` Namhyung Kim
2023-03-03 5:54 ` Ravi Bangoria
2023-03-06 22:29 ` Namhyung Kim
2023-03-07 3:19 ` Ravi Bangoria
2023-03-02 9:21 ` [PATCH 2/2] perf test: Add selftest to test IBS invocation " Ravi Bangoria
2023-03-02 22:12 ` Namhyung Kim
2023-03-03 5:55 ` Ravi Bangoria
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=20230302092109.367-1-ravi.bangoria@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@kernel.org \
--cc=ananth.narayan@amd.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=santosh.shukla@amd.com \
--cc=x86@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).