From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Eranian Stephane <eranian@google.com>,
Sandipan Das <sandipan.das@amd.com>,
Andrii Nakryiko <andrii@kernel.org>, Song Liu <song@kernel.org>,
Ravi Bangoria <ravi.bangoria@amd.com>,
Ananth Narayan <ananth.narayan@amd.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
bpf@vger.kernel.org, Dapeng Mi <dapeng1.mi@intel.com>,
Zide Chen <zide.chen@intel.com>,
Falcon Thomas <thomas.falcon@intel.com>,
Xudong Hao <xudong.hao@intel.com>
Subject: Re: [Patch v4 5/5] pef/x86/intel: Always snapshot live hardware LBR state for BPF path
Date: Wed, 21 Oct 2026 14:59:15 +0800 [thread overview]
Message-ID: <b8fbf942-22e5-4b4d-865b-3b024b4e50c7@linux.intel.com> (raw)
In-Reply-To: <20261021050711.4043703-6-dapeng1.mi@linux.intel.com>
Sashiko found several new long-standing LBR issues (not caused by the patch
series), https://lore.kernel.org/all/sashiko-outbox-179823@kernel.org/
Would post new patch series to fix the newly found issues. Thanks.
On 10/21/2026 1:07 PM, Dapeng Mi wrote:
> __intel_pmu_snapshot_branch_stack() is meant to snapshot the current
> runtime LBR state from hardware for the BPF path. However, stale cached
> PEBS LBR data can be snapshotted instead when a PEBS LBR user is active.
>
> Fix this by always snapshotting the live hardware LBR state, regardless
> of whether a PEBS LBR user is active. Reading the runtime LBR registers
> can overwrite the cached PEBS LBR stack, so save and restore the cached
> PEBS LBR state around the snapshot. This preserves the PEBS LBR data for
> later output to userspace in the normal PEBS record path.
>
> Fixes: c22ac2a3d4bd ("perf: Enable branch record for software events")
> Signed-off-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
> ---
> arch/x86/events/intel/core.c | 43 ++++++++++++++++++++++++++++++++++--
> arch/x86/events/intel/lbr.c | 9 --------
> 2 files changed, 41 insertions(+), 11 deletions(-)
>
> diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> index 5dfb9e9156e8..07d1a8a7845b 100644
> --- a/arch/x86/events/intel/core.c
> +++ b/arch/x86/events/intel/core.c
> @@ -2815,16 +2815,50 @@ static void intel_pmu_enable_all(int added)
> __intel_pmu_enable_all(added, false);
> }
>
> +struct lbr_snapshot {
> + struct perf_branch_stack stack;
> + struct perf_branch_entry entries[MAX_LBR_ENTRIES];
> + u64 counters[MAX_LBR_ENTRIES];
> +};
> +static DEFINE_PER_CPU(struct lbr_snapshot, lbr_snapshot);
> +
> static noinline int
> __intel_pmu_snapshot_branch_stack(struct perf_branch_entry *entries,
> unsigned int cnt, unsigned long flags)
> {
> struct cpu_hw_events *cpuc = this_cpu_ptr(&cpu_hw_events);
> + struct lbr_snapshot *snapshot = this_cpu_ptr(&lbr_snapshot);
> +
> + /*
> + * This may be called from bpf_event_handler() in a PMI context. If
> + * a PEBS LBR user is active, the PEBS sample record has already updated
> + * cpuc->lbr_stack. Reading the LBR registers here would overwrite that
> + * cached PEBS LBR stack, so save it first and restore it afterward. This
> + * keeps the cached LBR data available for later output to userspace in
> + * the normal PEBS record path.
> + */
> + if (cpuc->lbr_pebs_users) {
> + memcpy(&snapshot->stack, &cpuc->lbr_stack,
> + sizeof(struct perf_branch_stack));
> + memcpy(snapshot->entries, cpuc->lbr_entries,
> + sizeof(struct perf_branch_entry) * cpuc->lbr_stack.nr);
> + memcpy(snapshot->counters, cpuc->lbr_counters,
> + sizeof(u64) * cpuc->lbr_stack.nr);
> + }
>
> intel_pmu_lbr_read();
> cnt = min_t(unsigned int, cnt, cpuc->lbr_stack.nr);
> -
> memcpy(entries, cpuc->lbr_entries, sizeof(struct perf_branch_entry) * cnt);
> +
> + if (cpuc->lbr_pebs_users) {
> + memcpy(&cpuc->lbr_stack, &snapshot->stack,
> + sizeof(struct perf_branch_stack));
> + memcpy(cpuc->lbr_entries, snapshot->entries,
> + sizeof(struct perf_branch_entry) * cpuc->lbr_stack.nr);
> + memcpy(cpuc->lbr_counters, snapshot->counters,
> + sizeof(u64) * cpuc->lbr_stack.nr);
> + }
> +
> intel_pmu_enable_all(0);
> local_irq_restore(flags);
> return cnt;
> @@ -4022,7 +4056,12 @@ static int intel_pmu_handle_irq(struct pt_regs *regs)
>
> loops = 0;
> again:
> - intel_pmu_lbr_read();
> + /*
> + * No need to read the LBR stack when all LBR users are PEBS events,
> + * since the PEBS handler updates it.
> + */
> + if (cpuc->lbr_users != cpuc->lbr_pebs_users)
> + intel_pmu_lbr_read();
> intel_pmu_ack_status(status);
> if (++loops > 100) {
> static bool warned;
> diff --git a/arch/x86/events/intel/lbr.c b/arch/x86/events/intel/lbr.c
> index ac1759a71288..07b32255e48d 100644
> --- a/arch/x86/events/intel/lbr.c
> +++ b/arch/x86/events/intel/lbr.c
> @@ -1030,15 +1030,6 @@ void intel_pmu_lbr_read(void)
> return;
> }
>
> - /*
> - * Don't read when all LBRs users are using adaptive PEBS.
> - *
> - * This could be smarter and actually check the event,
> - * but this simple approach seems to work for now.
> - */
> - if (cpuc->lbr_users == cpuc->lbr_pebs_users)
> - return;
> -
> x86_pmu.lbr_read(cpuc);
>
> intel_pmu_lbr_filter(cpuc);
prev parent reply other threads:[~2026-10-21 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 5:07 [Patch v4 0/5] perf/x86: Limit branch snapshots to valid entries Dapeng Mi
2026-10-21 5:07 ` [Patch v4 1/5] perf/x86: Disable LBR if x86_pmu.lbr_nr exceeds MAX_LBR_ENTRIES Dapeng Mi
2026-10-21 5:07 ` [Patch v4 2/5] perf/x86/amd/lbr: Limit branch snapshots to valid entries Dapeng Mi
2026-10-21 5:07 ` [Patch v4 3/5] perf/x86/intel/lbr: Reset the cached LBR stack in intel_pmu_lbr_reset() Dapeng Mi
2026-10-21 5:07 ` [Patch v4 4/5] perf/x86/intel/lbr: Limit branch snapshots to valid entries Dapeng Mi
2026-10-21 5:07 ` [Patch v4 5/5] pef/x86/intel: Always snapshot live hardware LBR state for BPF path Dapeng Mi
2026-10-21 6:59 ` Mi, Dapeng [this message]
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=b8fbf942-22e5-4b4d-865b-3b024b4e50c7@linux.intel.com \
--to=dapeng1.mi@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dapeng1.mi@intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=sandipan.das@amd.com \
--cc=song@kernel.org \
--cc=thomas.falcon@intel.com \
--cc=xudong.hao@intel.com \
--cc=zide.chen@intel.com \
/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
all inboxes | Powered by JetHome®