From: Will Deacon <will@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
Joerg Roedel <joro@8bytes.org>,
Robin Murphy <robin.murphy@arm.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/exynos: add support for reserved regions
Date: Mon, 14 Jul 2025 12:54:31 +0100 [thread overview]
Message-ID: <175249276902.1459797.13570182845894865373.b4-ty@kernel.org> (raw)
In-Reply-To: <20250712-exynos-sysmmu-resv-regions-v1-1-e79681fcab1a@disroot.org>
On Sat, 12 Jul 2025 17:19:30 +0530, Kaustabh Chakraborty wrote:
> The bootloader configures a reserved memory region for framebuffer,
> which is protected by the IOMMU. The kernel-side driver is oblivious as
> of which memory region is set up by the bootloader. In such case, the
> IOMMU tries to reference the reserved region - which is not reserved in
> the kernel anymore - and it results in an unrecoverable page fault. More
> information about it is provided in [1].
>
> [...]
Applied to iommu (samsung/exynos), thanks!
[1/1] iommu/exynos: add support for reserved regions
https://git.kernel.org/iommu/c/2d70fdd9b5c9
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-07-14 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-12 11:49 Kaustabh Chakraborty
2025-07-14 11:54 ` 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=175249276902.1459797.13570182845894865373.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kauschluss@disroot.org \
--cc=kernel-team@android.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.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®