Thread (23 messages) 23 messages, 5 authors, 4h ago

Re: [PATCH v2 4/4] mm/mlock: migrate folios out of CMA when mlocking a range

From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: 2026-07-09 13:15:17
Also in: linux-mm, linux-rt-devel, lkml

On 2026-07-09 12:04:33 [+0200], David Hildenbrand (Arm) wrote:
On 7/7/26 14:59, Wandun Chen wrote:
quoted
From: Wandun Chen <redacted>

The region covered by mlock[all] may contain CMA pages. cma_alloc installs
What about ZONE_MOVABLE where memory is supposed to be migratable?
Would it be bad if the pages would not be movable anymore? Does this
effect just memory-hotplug or something else, too?
Also, what about drivers that mmap() CMA memory to user space, and
__mm_populate()->populate_vma_page_range() would actually try mlocking them, and
they actually must remain on CMA areas?
It should be safe to skip those. They belong to device and they
shouldn't be affected by anything including getting swapped out.

Sebastian
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help