From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>
Cc: Rob Herring <robh@kernel.org>,
Steven Price <steven.price@arm.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Philipp Zabel <p.zabel@pengutronix.de>,
kernel@collabora.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/8] drm/panfrost: Handle page mapping failure
Date: Mon, 2 Dec 2024 12:14:02 +0100 [thread overview]
Message-ID: <20241202121402.0d564c5c@collabora.com> (raw)
In-Reply-To: <20241128211223.1805830-6-adrian.larumbe@collabora.com>
On Thu, 28 Nov 2024 21:06:20 +0000
Adrián Larumbe <adrian.larumbe@collabora.com> wrote:
> When mapping the pages of a BO, either a heap type at page fault time or
> else a non-heap BO at object creation time, if the ARM page table mapping
> function fails, we unmap what had been mapped so far and bail out.
>
> Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>
> ---
> drivers/gpu/drm/panfrost/panfrost_mmu.c | 44 ++++++++++++++++++++++---
> 1 file changed, 39 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/panfrost/panfrost_mmu.c b/drivers/gpu/drm/panfrost/panfrost_mmu.c
> index 03ac527b35e7..5e30888bea0e 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_mmu.c
> +++ b/drivers/gpu/drm/panfrost/panfrost_mmu.c
> @@ -290,13 +290,31 @@ static void panfrost_mmu_flush_range(struct panfrost_device *pfdev,
> pm_runtime_put_autosuspend(pfdev->base.dev);
> }
>
> +static void mmu_unmap_range(size_t len, u64 iova, struct io_pgtable_ops *ops)
Can we use the following prototype instead?
static void mmu_unmap_range(struct panfrost_mmu *mmu,
u64 iova, size_t len)
> +{
> + size_t pgsize, unmapped_len = 0;
> + size_t unmapped_page, pgcount;
> +
> + while (unmapped_len < len) {
> + pgsize = get_pgsize(iova, len - unmapped_len, &pgcount);
> +
> + unmapped_page = ops->unmap_pages(ops, iova, pgsize, pgcount, NULL);
> + WARN_ON(unmapped_page != pgsize * pgcount);
> +
> + iova += pgsize * pgcount;
> + unmapped_len += pgsize * pgcount;
> + }
> +}
> +
> static int mmu_map_sg(struct panfrost_device *pfdev, struct panfrost_mmu *mmu,
> u64 iova, int prot, struct sg_table *sgt)
> {
> unsigned int count;
> struct scatterlist *sgl;
> struct io_pgtable_ops *ops = mmu->pgtbl_ops;
> + size_t total_mapped = 0;
> u64 start_iova = iova;
> + int ret = 0;
>
> for_each_sgtable_dma_sg(sgt, sgl, count) {
> unsigned long paddr = sg_dma_address(sgl);
> @@ -310,10 +328,15 @@ static int mmu_map_sg(struct panfrost_device *pfdev, struct panfrost_mmu *mmu,
> size_t pgcount, mapped = 0;
> size_t pgsize = get_pgsize(iova | paddr, len, &pgcount);
>
> - ops->map_pages(ops, iova, paddr, pgsize, pgcount, prot,
> + ret = ops->map_pages(ops, iova, paddr, pgsize, pgcount, prot,
> GFP_KERNEL, &mapped);
> + if (ret) {
> + mmu_unmap_range(total_mapped, start_iova, ops);
> + return ret;
I general, I'm not a huge fan of those error paths where things are
undone manually, because they tend to be overlooked when new steps are
added. I'd rather have a "goto error_unmap_pages;" here, and the
according label defined at the end of the function.
> + }
> /* Don't get stuck if things have gone wrong */
> mapped = max(mapped, pgsize);
> + total_mapped += mapped;
> iova += mapped;
> paddr += mapped;
> len -= mapped;
> @@ -333,6 +356,7 @@ int panfrost_mmu_map(struct panfrost_gem_mapping *mapping)
> struct panfrost_device *pfdev = to_panfrost_device(obj->dev);
> struct sg_table *sgt;
> int prot = IOMMU_READ | IOMMU_WRITE;
> + int ret;
>
> if (WARN_ON(mapping->active))
> return 0;
> @@ -344,8 +368,13 @@ int panfrost_mmu_map(struct panfrost_gem_mapping *mapping)
> if (WARN_ON(IS_ERR(sgt)))
> return PTR_ERR(sgt);
>
> - mmu_map_sg(pfdev, mapping->mmu, mapping->mmnode.start << PAGE_SHIFT,
> - prot, sgt);
> + ret = mmu_map_sg(pfdev, mapping->mmu, mapping->mmnode.start << PAGE_SHIFT,
> + prot, sgt);
> + if (ret) {
> + drm_gem_shmem_put_pages(shmem);
Same here.
> + return ret;
> + }
> +
> mapping->active = true;
>
> return 0;
> @@ -532,8 +561,10 @@ static int panfrost_mmu_map_fault_addr(struct panfrost_device *pfdev, int as,
> if (ret)
> goto err_map;
>
> - mmu_map_sg(pfdev, bomapping->mmu, addr,
> - IOMMU_WRITE | IOMMU_READ | IOMMU_NOEXEC, sgt);
> + ret = mmu_map_sg(pfdev, bomapping->mmu, addr,
> + IOMMU_WRITE | IOMMU_READ | IOMMU_NOEXEC, sgt);
> + if (ret)
> + goto err_mmu_map_sg;
>
> bomapping->active = true;
> bo->heap_rss_size += SZ_2M;
> @@ -547,6 +578,9 @@ static int panfrost_mmu_map_fault_addr(struct panfrost_device *pfdev, int as,
>
> return 0;
>
> +err_mmu_map_sg:
> + dma_unmap_sgtable(pfdev->base.dev, sgt,
> + DMA_BIDIRECTIONAL, 0);
> err_map:
> sg_free_table(sgt);
> err_unlock:
next prev parent reply other threads:[~2024-12-02 11:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 21:06 [PATCH v2 0/8] Some Panfrost fixes and improvements Adrián Larumbe
2024-11-28 21:06 ` [PATCH v2 1/8] drm/panfrost: Replace DRM driver allocation method with newer one Adrián Larumbe
2024-11-28 21:06 ` [PATCH v2 2/8] drm/panfrost: Handle inexistent GPU during probe Adrián Larumbe
2024-11-28 21:06 ` [PATCH v2 3/8] drm/panfrost: Handle job HW submit errors Adrián Larumbe
2024-12-02 9:21 ` Boris Brezillon
2024-12-02 9:24 ` Boris Brezillon
2024-11-28 21:06 ` [PATCH v2 4/8] drm/panfrost: Handle error when allocating AS number Adrián Larumbe
2024-12-02 9:29 ` Boris Brezillon
2024-11-28 21:06 ` [PATCH v2 5/8] drm/panfrost: Handle page mapping failure Adrián Larumbe
2024-12-02 11:14 ` Boris Brezillon [this message]
2024-11-28 21:06 ` [PATCH v2 6/8] drm/panfrost: Make re-enabling job interrupts at device reset optional Adrián Larumbe
2024-12-02 11:20 ` Boris Brezillon
2024-12-04 15:34 ` Adrián Larumbe
2024-12-04 16:40 ` Steven Price
2024-11-28 21:06 ` [PATCH v2 7/8] drm/panfrost: Add forward declaration and types header Adrián Larumbe
2024-12-02 11:21 ` Boris Brezillon
2024-11-28 21:06 ` [PATCH v2 8/8] drm/panfrost: Remove unused device property Adrián Larumbe
2024-12-02 11:23 ` Boris Brezillon
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=20241202121402.0d564c5c@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.