From: Boris Brezillon <boris.brezillon@collabora.com>
To: Akash Goel <akash.goel@arm.com>
Cc: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Steven Price" <steven.price@arm.com>,
kernel@collabora.com, "Liviu Dudau" <liviu.dudau@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>
Subject: Re: [PATCH] drm/panthor: Support partial unmaps of huge pages
Date: Tue, 21 Oct 2025 18:09:38 +0200 [thread overview]
Message-ID: <20251021180938.7a674618@fedora> (raw)
In-Reply-To: <bef0484d-8e17-477a-b4a2-f90d3204ff88@arm.com>
On Tue, 21 Oct 2025 15:32:45 +0100
Akash Goel <akash.goel@arm.com> wrote:
> On 10/19/25 04:19, Adrián Larumbe wrote:
> > Commit 33729a5fc0ca ("iommu/io-pgtable-arm: Remove split on unmap
> > behavior") did away with the treatment of partial unmaps of huge IOPTEs.
> >
>
> Sorry have a doubt.
>
> Corresponding to the commit 33729a5fc0ca, can we now remove the code to
> pre-allocate L3 page table pages i.e. 'op_ctx->rsvd_page_tables.pages'
> inside panthor_vm_prepare_unmap_op_ctx() ?.
Well, not if we want to support partial unmaps of huge pages at a non-2M
boundary.
next prev parent reply other threads:[~2025-10-21 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 3:19 [PATCH] drm/panthor: Support partial unmaps of huge pages Adrián Larumbe
2025-10-21 14:32 ` Akash Goel
2025-10-21 16:09 ` Boris Brezillon [this message]
2025-10-22 4:55 ` Akash Goel
2025-10-21 17:39 ` Adrián Larumbe
2025-10-22 4:45 ` Akash Goel
2025-10-22 9:05 ` Adrián Larumbe
2025-10-22 11:04 ` Adrián Larumbe
2025-10-21 14:42 ` 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=20251021180938.7a674618@fedora \
--to=boris.brezillon@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=akash.goel@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox