From: Sandipan Das <sandipan.das@amd.com>
To: Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, ananth.narayan@amd.com,
ravi.bangoria@amd.com
Subject: Re: [PATCH 0/2] perf/x86/amd/lbr: fix LBR filtering support
Date: Thu, 29 Sep 2022 14:00:07 +0530 [thread overview]
Message-ID: <388f2491-3b66-50ca-6f65-b5003bf3257a@amd.com> (raw)
In-Reply-To: <YzVT/TQtkoerDPFV@hirez.programming.kicks-ass.net>
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.
- Sandipan
next prev parent reply other threads:[~2022-09-29 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 18:40 Stephane Eranian
2022-09-28 18:40 ` [PATCH 1/2] perf/x86/utils: fix uninitialized var in get_branch_type() Stephane Eranian
2022-09-29 7:00 ` Sandipan Das
2022-09-30 9:31 ` [tip: perf/core] perf/x86/utils: Fix " tip-bot2 for Stephane Eranian
2022-09-28 18:40 ` [PATCH 2/2] perf/x86/amd/lbr: adjust LBR regardless of filtering Stephane Eranian
2022-09-29 7:01 ` Sandipan Das
2022-09-30 9:31 ` [tip: perf/core] perf/x86/amd/lbr: Adjust " tip-bot2 for Stephane Eranian
2022-09-29 8:14 ` [PATCH 0/2] perf/x86/amd/lbr: fix LBR filtering support Peter Zijlstra
2022-09-29 8:30 ` Sandipan Das [this message]
2022-09-29 10:19 ` Peter Zijlstra
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=388f2491-3b66-50ca-6f65-b5003bf3257a@amd.com \
--to=sandipan.das@amd.com \
--cc=ananth.narayan@amd.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.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®