From: James Morse <james.morse@arm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Ben Horgan <ben.horgan@arm.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Fenghua Yu <fenghuay@nvidia.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] arm_mpam: Force __iomem casts
Date: Fri, 6 Mar 2026 18:26:32 +0000 [thread overview]
Message-ID: <969b0700-9603-4e1c-b15c-e509e4d1b0ce@arm.com> (raw)
In-Reply-To: <18f3f73a-9bc6-4518-b3e4-730fa0793146@oss.qualcomm.com>
Hi Krzysztof, Ben,
On 27/02/2026 14:51, Krzysztof Kozlowski wrote:
> On 27/02/2026 15:06, Ben Horgan wrote:
>> On 2/16/26 11:02, Krzysztof Kozlowski wrote:
>>> Code allocates standard kernel memory to pass to the MPAM, which expects
>>> __iomem. The code is safe, because __iomem accessors should work fine
>>> on kernel mapped memory, however leads to sparse warnings:
>>>
>>> test_mpam_devices.c:327:42: warning: incorrect type in initializer (different address spaces)
>>> test_mpam_devices.c:327:42: expected char [noderef] __iomem *buf
>>> test_mpam_devices.c:327:42: got void *
>>> test_mpam_devices.c:342:24: warning: cast removes address space '__iomem' of expression
>>>
>>> Cast the pointer to memory via __force to silence them.
>>> diff --git a/drivers/resctrl/test_mpam_devices.c b/drivers/resctrl/test_mpam_devices.c
>>> index 3e8d564a0c64..2de41b47c138 100644
>>> --- a/drivers/resctrl/test_mpam_devices.c
>>> +++ b/drivers/resctrl/test_mpam_devices.c
>>> @@ -324,7 +324,7 @@ static void test_mpam_enable_merge_features(struct kunit *test)
>>>
>>> static void test_mpam_reset_msc_bitmap(struct kunit *test)
>>> {
>>> - char __iomem *buf = kunit_kzalloc(test, SZ_16K, GFP_KERNEL);
>>> + char __iomem *buf = (__force char __iomem *)kunit_kzalloc(test, SZ_16K, GFP_KERNEL);
>>> struct mpam_msc fake_msc = {};
>>> u32 *test_result;
>>>
>> This change looks good to me.
[...]
>> Acked-by: Ben Horgan <ben.horgan@arm.com>
Thanks! I've picked this for a fixes branch. I'm not sure what Will or Catalin will think
this needs fixing during the release as the driver is behind CONFIG_EXPERT. I'll ask...
Thanks,
James
prev parent reply other threads:[~2026-03-06 18:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 11:02 [PATCH 1/2] arm_mpam: Force __iomem casts Krzysztof Kozlowski
2026-02-16 11:02 ` [PATCH 2/2] arm64: MAINTAINERS: Include resctrl MPAM driver Krzysztof Kozlowski
2026-02-18 16:23 ` Catalin Marinas
2026-02-18 16:46 ` Krzysztof Kozlowski
2026-02-18 17:13 ` Catalin Marinas
2026-02-18 17:21 ` Krzysztof Kozlowski
2026-02-27 14:06 ` [PATCH 1/2] arm_mpam: Force __iomem casts Ben Horgan
2026-02-27 14:51 ` Krzysztof Kozlowski
2026-03-06 18:26 ` James Morse [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=969b0700-9603-4e1c-b15c-e509e4d1b0ce@arm.com \
--to=james.morse@arm.com \
--cc=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fenghuay@nvidia.com \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.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