Linux Perf Users
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Sandipan Das <sandipan.das@amd.com>,
	Dapeng Mi <dapeng1.mi@linux.intel.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	Thomas Gleixner <tglx@kernel.org>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
	Andrii Nakryiko <andrii@kernel.org>, Song Liu <song@kernel.org>,
	Ravi Bangoria <ravi.bangoria@amd.com>,
	Ananth Narayan <ananth.narayan@amd.com>
Subject: Re: [PATCH] perf/x86/amd/lbr: Limit branch snapshots to valid entries
Date: Tue, 13 Oct 2026 09:46:25 +0200	[thread overview]
Message-ID: <20261013074625.GC2009045@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <94d387f2-ff07-4895-a722-e8ded4203309@amd.com>

On Tue, Oct 13, 2026 at 12:14:58PM +0530, Sandipan Das wrote:
> On 12-10-2026 21:00, Peter Zijlstra wrote:
> > On Wed, Oct 07, 2026 at 11:40:02PM +0530, Sandipan Das wrote:
> >> The branch snapshot callback used by bpf_get_branch_snapshot() copies
> >> up to x86_pmu.lbr_nr entries from cpuc->lbr_entries[], even when the
> >> last LBR read kept fewer branches. The entries past lbr_stack.nr are
> >> invalid, but they end up reaching BPF programs.
> >>
> >> Limit copying to lbr_stack.nr entries and also reset lbr_stack.nr when
> >> amd_pmu_lbr_read() skips reading the registers, so that a stale count
> >> is never reused.
> >>
> >> Fixes: a4d18112e531 ("perf/x86/amd: Support capturing LBR from software events")
> >> Reported-by: Sashiko <sashiko-bot@kernel.org>
> >> Closes: https://lore.kernel.org/all/sashiko-outbox-163130@kernel.org/
> >> Signed-off-by: Sandipan Das <sandipan.das@amd.com>
> >> ---
> >>  arch/x86/events/amd/core.c | 2 +-
> >>  arch/x86/events/amd/lbr.c  | 4 +++-
> >>  2 files changed, 4 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/arch/x86/events/amd/core.c b/arch/x86/events/amd/core.c
> >> index 49b6b8fce566..bf631f60757c 100644
> >> --- a/arch/x86/events/amd/core.c
> >> +++ b/arch/x86/events/amd/core.c
> >> @@ -944,7 +944,7 @@ static int amd_pmu_v2_snapshot_branch_stack(struct perf_branch_entry *entries, u
> >>  	cpuc = this_cpu_ptr(&cpu_hw_events);
> >>  
> >>  	amd_pmu_lbr_read();
> >> -	cnt = min(cnt, x86_pmu.lbr_nr);
> >> +	cnt = min(cnt, cpuc->lbr_stack.nr);
> >>  	memcpy(entries, cpuc->lbr_entries, sizeof(struct perf_branch_entry) * cnt);
> >>  
> >>  	amd_pmu_v2_enable_all(0);
> >> diff --git a/arch/x86/events/amd/lbr.c b/arch/x86/events/amd/lbr.c
> >> index 1e1b2f08cb51..a00d3850c4a8 100644
> >> --- a/arch/x86/events/amd/lbr.c
> >> +++ b/arch/x86/events/amd/lbr.c
> >> @@ -165,8 +165,10 @@ void amd_pmu_lbr_read(void)
> >>  	struct branch_entry entry;
> >>  	int out = 0, idx, i;
> >>  
> >> -	if (!cpuc->lbr_users)
> >> +	if (!cpuc->lbr_users) {
> >> +		cpuc->lbr_stack.nr = 0;
> >>  		return;
> >> +	}
> >>  
> >>  	for (i = 0; i < x86_pmu.lbr_nr; i++) {
> >>  		entry.from.full	= amd_pmu_lbr_get_from(i);
> > 
> > You now seem to deviate from what the Intel code does. Please clarify.
> 
> Yes, it is a deviation. I thought of proposing the following but didn't
> proceed because I was not sure about the if condition in the second hunk
> which considers things other than cpuc->lbr_users for an early return.

Dapeng, can you look into this? I would really like to keep behaviour
consistent where possible.

> diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> index 0a34d674df59..5dfb9e9156e8 100644
> --- a/arch/x86/events/intel/core.c
> +++ b/arch/x86/events/intel/core.c
> @@ -2822,7 +2822,7 @@ __intel_pmu_snapshot_branch_stack(struct perf_branch_entry *entries,
>         struct cpu_hw_events *cpuc = this_cpu_ptr(&cpu_hw_events);
> 
>         intel_pmu_lbr_read();
> -       cnt = min_t(unsigned int, cnt, x86_pmu.lbr_nr);
> +       cnt = min_t(unsigned int, cnt, cpuc->lbr_stack.nr);
> 
>         memcpy(entries, cpuc->lbr_entries, sizeof(struct perf_branch_entry) * cnt);
>         intel_pmu_enable_all(0);
> diff --git a/arch/x86/events/intel/lbr.c b/arch/x86/events/intel/lbr.c
> index 0b446d8912e4..6b070490f461 100644
> --- a/arch/x86/events/intel/lbr.c
> +++ b/arch/x86/events/intel/lbr.c
> @@ -1026,8 +1026,10 @@ void intel_pmu_lbr_read(void)
>          * but this simple approach seems to work for now.
>          */
>         if (!cpuc->lbr_users || vlbr_exclude_host() ||
> -           cpuc->lbr_users == cpuc->lbr_pebs_users)
> +           cpuc->lbr_users == cpuc->lbr_pebs_users) {
> +               cpuc->lbr_stack.nr = 0;
>                 return;
> +       }
> 
>         x86_pmu.lbr_read(cpuc);
> 

  reply	other threads:[~2026-10-13  7:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 18:10 [PATCH] perf/x86/amd/lbr: Limit branch snapshots to valid entries Sandipan Das
2026-10-07 18:19 ` sashiko-bot
2026-10-12 15:30 ` Peter Zijlstra
2026-10-13  6:44   ` Sandipan Das
2026-10-13  7:46     ` Peter Zijlstra [this message]
2026-10-13 12:53       ` Mi, Dapeng

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=20261013074625.GC2009045@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ananth.narayan@amd.com \
    --cc=andrii@kernel.org \
    --cc=bp@alien8.de \
    --cc=bpf@vger.kernel.org \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=ravi.bangoria@amd.com \
    --cc=sandipan.das@amd.com \
    --cc=song@kernel.org \
    --cc=tglx@kernel.org \
    --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