linux-kernel - Re: [PATCH 0/2] perf/x86/amd/lbr: fix LBR filtering support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YzVxHn4PPnMTlZxi@hirez.programming.kicks-ass.net>
Date:   Thu, 29 Sep 2022 12:19:10 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Sandipan Das <sandipan.das@....com>
Cc:     Stephane Eranian <eranian@...gle.com>,
        linux-kernel@...r.kernel.org, ananth.narayan@....com,
        ravi.bangoria@....com
Subject: Re: [PATCH 0/2] perf/x86/amd/lbr: fix LBR filtering support

On Thu, Sep 29, 2022 at 02:00:07PM +0530, Sandipan Das wrote:
> On 9/29/2022 1:44 PM, Peter Zijlstra wrote:
> > On Wed, Sep 28, 2022 at 11:40:41AM -0700, Stephane Eranian wrote:
> >> Short patch series to address some kernel issues with the AMD LBrv2
> >> enablement which were introduced in Linux 6.0.
> >>
> >> Stephane Eranian (2):
> >>   perf/x86/utils: fix uninitialized var in get_branch_type()
> >>   perf/x86/amd/lbr: adjust LBR regardless of filtering
> >>
> >>  arch/x86/events/amd/lbr.c | 8 ++++++--
> >>  arch/x86/events/utils.c   | 4 ++++
> >>  2 files changed, 10 insertions(+), 2 deletions(-)
> > 
> > If you want this in perf/urgent you're missing Fixes tags.
> 
> That would be:
> 
> Fixes: df3e9612f758 ("perf/x86: Make branch classifier fusion-aware")
> 
> and 
> 
> Fixes: 245268c19f70 ("perf/x86/amd/lbr: Use fusion-aware branch classifier")
> 
> for the 1st and 2nd patch respectively.

Thanks; but trying to queue then in /urgent resulted in me finding out
they're not at all slated for 6.0. The AMD LBRv2 stuff is in perf/core,
waiting for 6.1 to start. So I'll just go queue them there.

Still, good to have Fixes tags on them.