From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jason Gunthorpe" <jgg@nvidia.com>,
"Naresh Kamboju" <naresh.kamboju@linaro.org>
Cc: "open list" <linux-kernel@vger.kernel.org>,
iommu@lists.linux.dev, lkft-triage@lists.linaro.org,
"Linux Regressions" <regressions@lists.linux.dev>,
"Nicolin Chen" <nicolinc@nvidia.com>,
"Jean-Philippe Brucker" <jean-philippe@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Benjamin Copeland" <benjamin.copeland@linaro.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>
Subject: Re: next-20250702 WARNING iommu io-pgtable-arm.c at arm_lpae_map_pages qcom_iommu_map
Date: Wed, 09 Jul 2025 18:50:02 +0200 [thread overview]
Message-ID: <ee234cd8-63dd-41fc-9a5f-94ffca21e2a1@app.fastmail.com> (raw)
In-Reply-To: <20250709162609.GD1599700@nvidia.com>
On Wed, Jul 9, 2025, at 18:26, Jason Gunthorpe wrote:
> On Wed, Jul 09, 2025 at 04:14:26PM +0530, Naresh Kamboju wrote:
>
> I believe the original text was a copy and pasto from an ARMv7s driver
> (ie the 32 bit ARM page table) which uses that unique combination of
> sizes. It is not a sane bitmap for HW with 64 bit page table support,
> there is never a 1M option for instance.
>
> So this removes 64k page support, which maybe didn't even work?
My guess would be that this bug is specific to this SoC running
in 32-bit mode. This is a rare exception and not really well
supported, as most 64-bit Arm chips require a 64-bit kernel, but
this one (along with Broadcom bcm283x) can do either.
When running a 32-bit kernel, there is definitely no support for
64KB pages in the CPU, unlike on arm64.
Arnd
next prev parent reply other threads:[~2025-07-09 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 20:56 next-20250702 WARNING iommu io-pgtable-arm.c at arm_lpae_map_pages qcom_iommu_map Naresh Kamboju
2025-07-09 0:25 ` Jason Gunthorpe
2025-07-09 10:44 ` Naresh Kamboju
2025-07-09 16:26 ` Jason Gunthorpe
2025-07-09 16:50 ` Arnd Bergmann [this message]
2025-07-09 17:22 ` Jason Gunthorpe
2025-07-10 10:38 ` Naresh Kamboju
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=ee234cd8-63dd-41fc-9a5f-94ffca21e2a1@app.fastmail.com \
--to=arnd@arndb.de \
--cc=anders.roxell@linaro.org \
--cc=benjamin.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=nicolinc@nvidia.com \
--cc=regressions@lists.linux.dev \
/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