From: Ben Horgan <ben.horgan@arm.com>
To: Zeng Heng <zengheng4@huawei.com>,
catalin.marinas@arm.com, tan.shaopeng@jp.fujitsu.com,
james.morse@arm.com, reinette.chatre@intel.com,
fenghuay@nvidia.com, jonathan.cameron@huawei.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm_mpam: Fix MPAM reset on resctrl unmount by clearing in_reset_state
Date: Fri, 27 Feb 2026 14:16:36 +0000 [thread overview]
Message-ID: <5071eea1-97f6-45d7-aad0-b109080f3032@arm.com> (raw)
In-Reply-To: <16ac4ebe-123f-4e43-9930-bf3d6f17f31c@arm.com>
On 2/17/26 15:59, Ben Horgan wrote:
> Hi Zeng,
>
> On 2/13/26 07:50, Zeng Heng wrote:
>> When resctrl is unmounted, MPAM components should be reset to default
>> configurations to avoid impacting system performance. However, after
>> a user updates MPAM configuration via mpam_apply_config(), the
>> in_reset_state flag remains true, causing mpam_reset_ris() to skip
>> the actual register restoration on subsequent resets.
>>
>> For example, after mounting resctrl and modifying the root group's
>> schemata (e.g., changing MBMAX/MBMIN values), unmounting resctrl
>
> nit: MBMIN isn't currently supported in resctrl. I'd just drop the
> part in brackets.
>
>> would leave the modified MPAM settings in hardware registers since
>> mpam_reset_ris() returns early due to in_reset_state still being true.
>> This results in persistent performance restrictions even after resctrl
>> is umounted.
>>
>> Fix by clearing in_reset_state to false immediately after successful
>> configuration application, ensuring that the next reset operation
>> properly restores MPAM register defaults.
>>
>> Fixes: f188a36ca241 ("arm_mpam: Reset MSC controls from cpuhp callbacks")
>
> mpam_apply_config() doesn't exist in this commit. I would have expected:
> Fixes: 09b89d2a72f3 ("arm_mpam: Allow configuration to be applied and restored during cpu online")
>
>> Signed-off-by: Zeng Heng <zengheng4@huawei.com>
>
> The change and justification looks good to me.
>
> Acked-by: Ben Horgan <ben.horgan@arm.com>
>
I'll add this on to the start of the current mpam resctrl series as even
though this is squashing an existing bug it can't be hit until mpam has
a user interface and so doesn't need to go as a fix.
Thanks,
Ben
next prev parent reply other threads:[~2026-02-27 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 7:50 Zeng Heng
2026-02-17 15:59 ` Ben Horgan
2026-02-27 14:16 ` Ben Horgan [this message]
2026-02-28 2:30 ` Zeng Heng
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=5071eea1-97f6-45d7-aad0-b109080f3032@arm.com \
--to=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=tan.shaopeng@jp.fujitsu.com \
--cc=zengheng4@huawei.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®