From: Andre Przywara <andre.przywara@arm.com>
To: Ritwick Sharma <ritwick.sharma@arm.com>
Cc: ben.horgan@arm.com, catalin.marinas@arm.com, fenghuay@nvidia.com,
ganapatrao.kulkarni@oss.qualcomm.com, guohanjun@huawei.com,
james.morse@arm.com, jic23@kernel.org, lee@trager.us,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, lpieralisi@kernel.org,
rafael@kernel.org, reinette.chatre@intel.com,
sramana@qti.qualcomm.com, srivathsa.rao@oss.qualcomm.com,
sudeep.holla@kernel.org, tsoni@quicinc.com, will@kernel.org
Subject: Re: [PATCH v4 08/10] arm_mpam: add MPAM-Fb MSC firmware access support
Date: Tue, 28 Jul 2026 12:24:25 +0200 [thread overview]
Message-ID: <22434d15-7e7c-457d-8431-b77db9448cf0@arm.com> (raw)
In-Reply-To: <20260728100421.4047928-1-ritwick.sharma@arm.com>
Hi Ritwick,
On 7/28/26 12:04, Ritwick Sharma wrote:
> On Thu, Jul 23, 2026 at 05:54:52PM +0200, Andre Przywara wrote:
>
>> - WARN_ON_ONCE((MSMON_MBWU_L + sizeof(u64)) > msc->mapped_hwpage_sz);
>> + if (msc->iface == MPAM_IFACE_MMIO)
>> + WARN_ON_ONCE((MSMON_MBWU_L + sizeof(u64)) > msc->mapped_hwpage_sz);
>
> I tested the MPAM-Fb series on an Arm AGI CPU.
Many thanks for that, and for reporting on the list!
> I think a similar MPAM_IFACE_MMIO check is needed in
> mpam_msc_zero_mbwu_l(). Without this check, the mapped_hwpage_sz bounds
> check is also performed for an MPAM-Fb MSC, which does not have an MMIO
> mapping. I observed the following warning during testing:
>
> [ 50.638246] WARNING: drivers/resctrl/mpam_devices.c:1266 at mpam_msc_zero_mbwu_l+0x98/0xa8
Ouch, you are right, I missed that one. It seems my very limited testing
didn't touch that code path.
> There also appears to be an off-by-one issue in the calculation of
> mapped_hwpage_sz:
>
> msc->mapped_hwpage_sz = msc_res->end - msc_res->start;
>
> The current calculation records a size that is one byte smaller than
> the actual resource. I think this should use resource_size() instead:
>
> msc->mapped_hwpage_sz = resource_size(msc_res);
Well spotted, I can make a separate patch for that, unless you beat me
to it!
Many thanks,
Andre
>
> Thanks,
> Ritwick
next prev parent reply other threads:[~2026-07-28 10:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 15:54 [PATCH v4 00/10] arm_mpam: Add MPAM-Fb firmware support Andre Przywara
2026-07-23 15:54 ` [PATCH v4 01/10] arm_mpam: let low level MSC accessors return an error Andre Przywara
2026-07-27 22:12 ` Jonathan Cameron
2026-07-28 15:35 ` Andre Przywara
2026-07-23 15:54 ` [PATCH v4 02/10] arm_mpam: propagate MSC access errors for hw_probe functions Andre Przywara
2026-07-27 22:21 ` Jonathan Cameron
2026-07-23 15:54 ` [PATCH v4 03/10] arm_mpam: propagate MSC access errors for MBWU counters Andre Przywara
2026-07-27 22:37 ` Jonathan Cameron
2026-07-23 15:54 ` [PATCH v4 04/10] arm_mpam: propagate MSC access errors for msmon helpers Andre Przywara
2026-07-27 22:41 ` Jonathan Cameron
2026-07-23 15:54 ` [PATCH v4 05/10] arm_mpam: propagate MSC access errors for __ris_msmon_read() Andre Przywara
2026-07-24 10:02 ` Sudeep Holla
2026-07-24 11:17 ` Andre Przywara
2026-07-24 12:19 ` Sudeep Holla
2026-07-27 22:44 ` Jonathan Cameron
2026-07-23 15:54 ` [PATCH v4 06/10] arm_mpam: propagate MSC access errors for state saving function Andre Przywara
2026-07-24 10:07 ` Sudeep Holla
2026-07-24 11:19 ` Andre Przywara
2026-07-24 12:27 ` Sudeep Holla
2026-07-24 16:43 ` Ben Horgan
2026-07-27 22:51 ` Jonathan Cameron
2026-07-28 8:43 ` Ben Horgan
2026-07-27 22:46 ` Jonathan Cameron
2026-07-23 15:54 ` [PATCH v4 07/10] arm_mpam: prepare mon_sel locking for MPAM-Fb Andre Przywara
2026-07-24 16:56 ` Ben Horgan
2026-07-23 15:54 ` [PATCH v4 08/10] arm_mpam: add MPAM-Fb MSC firmware access support Andre Przywara
2026-07-24 9:55 ` Sudeep Holla
2026-07-24 11:17 ` Andre Przywara
2026-07-24 12:22 ` Sudeep Holla
2026-07-24 17:08 ` Ben Horgan
2026-07-24 18:03 ` Sudeep Holla
2026-07-28 12:27 ` Andre Przywara
2026-07-28 16:04 ` Andre Przywara
2026-07-27 23:22 ` Jonathan Cameron
2026-07-29 8:07 ` Andre Przywara
2026-07-28 6:27 ` Srivathsa L Rao
2026-07-28 16:19 ` Andre Przywara
[not found] ` <20260728100421.4047928-1-ritwick.sharma@arm.com>
2026-07-28 10:24 ` Andre Przywara [this message]
2026-07-23 15:54 ` [PATCH v4 09/10] arm_mpam: prevent MPAM-Fb accesses inside IRQ handler Andre Przywara
2026-07-24 16:52 ` Ben Horgan
2026-07-23 15:54 ` [PATCH v4 10/10] arm_mpam: detect and enable MPAM-Fb PCC support Andre Przywara
2026-07-24 10:18 ` Sudeep Holla
2026-07-27 12:48 ` Lorenzo Pieralisi
2026-07-27 13:20 ` Sudeep Holla
2026-07-27 13:33 ` Lorenzo Pieralisi
2026-07-27 13:39 ` Sudeep Holla
2026-07-27 13:39 ` Andre Przywara
2026-07-27 16:27 ` Srivathsa L Rao
2026-07-27 23:36 ` Jonathan Cameron
2026-07-29 11:53 ` Andre Przywara
2026-07-29 8:56 ` Ben Horgan
2026-07-29 9:21 ` Andre Przywara
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=22434d15-7e7c-457d-8431-b77db9448cf0@arm.com \
--to=andre.przywara@arm.com \
--cc=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fenghuay@nvidia.com \
--cc=ganapatrao.kulkarni@oss.qualcomm.com \
--cc=guohanjun@huawei.com \
--cc=james.morse@arm.com \
--cc=jic23@kernel.org \
--cc=lee@trager.us \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=rafael@kernel.org \
--cc=reinette.chatre@intel.com \
--cc=ritwick.sharma@arm.com \
--cc=sramana@qti.qualcomm.com \
--cc=srivathsa.rao@oss.qualcomm.com \
--cc=sudeep.holla@kernel.org \
--cc=tsoni@quicinc.com \
--cc=will@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