From: Mike Rapoport via OP-TEE <op-tee@lists.trustedfirmware.org>
To: Vincent Donnefort <vdonnefort@google.com>
Cc: catalin.marinas@arm.com, will@kernel.org,
akpm@linux-foundation.org, m.szyprowski@samsung.com,
jenswi@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, mark.rutland@arm.com, robin.murphy@arm.com,
hch@lst.de, ryan.roberts@arm.com, sumit.garg@kernel.org,
sudeep.holla@kernel.org, ardb@kernel.org,
thierry.reding@kernel.org, david@kernel.org,
danielmentz@google.com, linux-arm-kernel@lists.infradead.org,
linux-mm@kvack.org, iommu@lists.linux.dev,
op-tee@lists.trustedfirmware.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/8] memblock: Introduce MEMBLOCK_PTEMAP
Date: Sun, 15 Nov 2026 21:14:25 +0200 [thread overview]
Message-ID: <avoEkRRM3iH70_Am@kernel.org> (raw)
In-Reply-To: <20261111110738.872947-2-vdonnefort@google.com>
On Wed, Nov 11, 2026 at 11:07:31AM +0000, Vincent Donnefort wrote:
> Keeping PTE-level mappings is interesting for arm64 as it allows
> mapping/unmapping pages from the kernel direct map without the risk of
> splitting blocks which, under the break-before-make rule, may trigger
> page-faults the kernel can't handle.
>
> However, mapping the entire direct map at PTE-level is costly. So
> instead, create a new memblock flag MEMBLOCK_PTEMAP to selectively apply
> a PTE-level mapping.
>
> Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> include/linux/memblock.h | 9 +++++++++
> mm/memblock.c | 39 +++++++++++++++++++++++++++++++++++++--
> 2 files changed, 46 insertions(+), 2 deletions(-)
--
Sincerely yours,
Mike.
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@kernel.org>
To: Vincent Donnefort <vdonnefort@google.com>
Cc: catalin.marinas@arm.com, will@kernel.org,
akpm@linux-foundation.org, m.szyprowski@samsung.com,
jenswi@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, mark.rutland@arm.com, robin.murphy@arm.com,
hch@lst.de, ryan.roberts@arm.com, sumit.garg@kernel.org,
sudeep.holla@kernel.org, ardb@kernel.org,
thierry.reding@kernel.org, david@kernel.org,
danielmentz@google.com, linux-arm-kernel@lists.infradead.org,
linux-mm@kvack.org, iommu@lists.linux.dev,
op-tee@lists.trustedfirmware.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/8] memblock: Introduce MEMBLOCK_PTEMAP
Date: Sun, 15 Nov 2026 21:14:25 +0200 [thread overview]
Message-ID: <avoEkRRM3iH70_Am@kernel.org> (raw)
In-Reply-To: <20261111110738.872947-2-vdonnefort@google.com>
On Wed, Nov 11, 2026 at 11:07:31AM +0000, Vincent Donnefort wrote:
> Keeping PTE-level mappings is interesting for arm64 as it allows
> mapping/unmapping pages from the kernel direct map without the risk of
> splitting blocks which, under the break-before-make rule, may trigger
> page-faults the kernel can't handle.
>
> However, mapping the entire direct map at PTE-level is costly. So
> instead, create a new memblock flag MEMBLOCK_PTEMAP to selectively apply
> a PTE-level mapping.
>
> Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> include/linux/memblock.h | 9 +++++++++
> mm/memblock.c | 39 +++++++++++++++++++++++++++++++++++++--
> 2 files changed, 46 insertions(+), 2 deletions(-)
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-11-15 19:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 11:07 [PATCH v3 0/8] arm64: Unmap FF-A lent memory from direct map Vincent Donnefort
2026-11-11 11:07 ` Vincent Donnefort via OP-TEE
2026-11-11 11:07 ` [PATCH v3 1/8] memblock: Introduce MEMBLOCK_PTEMAP Vincent Donnefort
2026-11-11 11:07 ` Vincent Donnefort via OP-TEE
2026-11-15 19:14 ` Mike Rapoport via OP-TEE [this message]
2026-11-15 19:14 ` Mike Rapoport
2026-11-11 11:07 ` [PATCH v3 2/8] arm64: Add support for MEMBLOCK_PTEMAP Vincent Donnefort
2026-11-11 11:07 ` Vincent Donnefort via OP-TEE
2026-11-15 19:20 ` Mike Rapoport
2026-11-15 19:20 ` Mike Rapoport via OP-TEE
2026-11-11 11:07 ` [PATCH v3 3/8] dma-contiguous: Expose rmem_cma_ops Vincent Donnefort
2026-11-11 11:07 ` Vincent Donnefort via OP-TEE
2026-11-11 11:07 ` [PATCH v3 4/8] dt-bindings: reserved-memory: Add lendable-dma-pool Vincent Donnefort
2026-11-11 11:07 ` Vincent Donnefort via OP-TEE
2026-11-11 11:07 ` [PATCH v3 5/8] dma-mapping: Introduce lendable-dma-pool Vincent Donnefort
2026-11-11 11:07 ` Vincent Donnefort via OP-TEE
2026-11-12 11:08 ` sashiko-bot
2026-11-12 11:08 ` sashiko-bot--- via OP-TEE
2026-11-11 11:07 ` [PATCH v3 6/8] arm64: Introduce direct_map_is_ptemap() Vincent Donnefort
2026-11-11 11:07 ` Vincent Donnefort via OP-TEE
2026-11-11 11:07 ` [PATCH v3 7/8] arm64: Add support for lendable-dma-pool Vincent Donnefort
2026-11-11 11:07 ` Vincent Donnefort via OP-TEE
2026-11-11 11:07 ` [PATCH v3 8/8] optee: " Vincent Donnefort
2026-11-11 11:07 ` Vincent Donnefort via OP-TEE
2026-11-12 11:08 ` sashiko-bot
2026-11-12 11:08 ` sashiko-bot--- via OP-TEE
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=avoEkRRM3iH70_Am@kernel.org \
--to=op-tee@lists.trustedfirmware.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=danielmentz@google.com \
--cc=david@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=jenswi@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=sudeep.holla@kernel.org \
--cc=sumit.garg@kernel.org \
--cc=thierry.reding@kernel.org \
--cc=vdonnefort@google.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 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.