From: Will Deacon <will@kernel.org>
To: Ben Horgan <ben.horgan@arm.com>,
James Morse <james.morse@arm.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Gavin Shan <gshan@redhat.com>,
Shaopeng Tan <tan.shaopeng@fujitsu.com>,
Jesse Chick <jessechick@os.amperecomputing.com>,
Fenghua Yu <fenghuay@nvidia.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Matt Ochs <mochs@nvidia.com>
Subject: Re: [PATCH] arm_mpam: Fix MPAMCFG_MBW_PBM register setting
Date: Thu, 16 Jul 2026 17:47:58 +0100 [thread overview]
Message-ID: <178420954768.37480.18364490568749911795.b4-ty@kernel.org> (raw)
In-Reply-To: <20260607050925.252475-1-fenghuay@nvidia.com>
On Sat, 06 Jun 2026 22:09:25 -0700, Fenghua Yu wrote:
> MPAMCFG_MBW_PBM is written from cfg if cfg has the MBW partition feature.
> It is reset when cfg does not have the MBW partition feature.
>
> But the register handling is reversed. This may cause an incorrect
> register setting. For example, during an MPAM reset, reset_cfg is
> empty (no MBW partition feature set), and cfg->mbw_pbm is 0. Instead of
> resetting MPAMCFG_MBW_PBM to all 1's, the current logic will set it to
> cfg->mbw_pbm, which is 0.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm_mpam: Fix MPAMCFG_MBW_PBM register setting
https://git.kernel.org/arm64/c/021118ce5ea9
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-07-16 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 5:09 Fenghua Yu
2026-06-08 4:46 ` Gavin Shan
2026-06-09 2:06 ` Fenghua Yu
2026-06-09 9:12 ` Ben Horgan
2026-07-16 16:47 ` Will Deacon [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=178420954768.37480.18364490568749911795.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fenghuay@nvidia.com \
--cc=gshan@redhat.com \
--cc=james.morse@arm.com \
--cc=jessechick@os.amperecomputing.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochs@nvidia.com \
--cc=reinette.chatre@intel.com \
--cc=tan.shaopeng@fujitsu.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®