From: Ingo Molnar <mingo@kernel.org>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: x86@kernel.org, peterz@infradead.org, mingo@redhat.com,
tglx@linutronix.de, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, jolsa@kernel.org, song@kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH v4 0/4] perf/x86/amd: add LBR capture support outside of hardware events
Date: Mon, 1 Apr 2024 11:29:57 +0200 [thread overview]
Message-ID: <Zgp+lYLOZU3OkO7w@gmail.com> (raw)
In-Reply-To: <20240331041830.2806741-1-andrii@kernel.org>
* Andrii Nakryiko <andrii@kernel.org> wrote:
> Add AMD-specific implementation of perf_snapshot_branch_stack static call that
> allows LBR capture from arbitrary points in the kernel. This is utilized by
> BPF programs. See patch #3 for all the details.
>
> Patches #1 and #2 are preparatory steps to ensure LBR freezing is completely
> inlined and have no branches, to minimize LBR snapshot contamination.
>
> Patch #4 removes an artificial restriction on perf events with LBR enabled.
>
> Andrii Nakryiko (4):
> perf/x86/amd: ensure amd_pmu_core_disable_all() is always inlined
> perf/x86/amd: avoid taking branches before disabling LBR
> perf/x86/amd: support capturing LBR from software events
> perf/x86/amd: don't reject non-sampling events with configured LBR
>
> arch/x86/events/amd/core.c | 37 +++++++++++++++++++++++++++++++++++-
> arch/x86/events/amd/lbr.c | 11 +----------
> arch/x86/events/perf_event.h | 11 +++++++++++
> 3 files changed, 48 insertions(+), 11 deletions(-)
So there's a new conflict with patch #2, probably due to interaction
with this recent fix that is now upstream:
598c2fafc06f ("perf/x86/amd/lbr: Use freeze based on availability")
I don't think it should change the logic of the snapshot feature
materially, X86_FEATURE_AMD_LBR_PMC_FREEZE should be orthogonal to it,
as the LBR snapshot isn't taken from a PMI.
Thanks,
Ingo
next prev parent reply other threads:[~2024-04-01 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 4:18 [PATCH v4 0/4] perf/x86/amd: add LBR capture support outside of hardware events Andrii Nakryiko
2024-03-31 4:18 ` [PATCH v4 1/4] perf/x86/amd: ensure amd_pmu_core_disable_all() is always inlined Andrii Nakryiko
2024-03-31 4:18 ` [PATCH v4 2/4] perf/x86/amd: avoid taking branches before disabling LBR Andrii Nakryiko
2024-03-31 4:18 ` [PATCH v4 3/4] perf/x86/amd: support capturing LBR from software events Andrii Nakryiko
2024-03-31 4:18 ` [PATCH v4 4/4] perf/x86/amd: don't reject non-sampling events with configured LBR Andrii Nakryiko
2024-04-01 9:29 ` Ingo Molnar [this message]
2024-04-02 2:16 ` [PATCH v4 0/4] perf/x86/amd: add LBR capture support outside of hardware events Andrii Nakryiko
2024-04-03 8:06 ` Ingo Molnar
2024-04-03 16:08 ` Andrii Nakryiko
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=Zgp+lYLOZU3OkO7w@gmail.com \
--to=mingo@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--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 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.