mm-balloon_compaction-movable_ops-doc-updates.patch removed from -mm tree
The quilt patch titled
Subject: mm/balloon_compaction: "movable_ops" doc updates
has been removed from the -mm tree. Its filename was
mm-balloon_compaction-movable_ops-doc-updates.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: David Hildenbrand <[email protected]>
Subject: mm/balloon_compaction: "movable_ops" doc updates
Date: Fri, 4 Jul 2025 12:25:22 +0200
Let's bring the docs up-to-date. Setting PG_movable_ops + page->private very likely still requires to be performed under documented locks: it's complicated.
We will rework this in the future, as we will try avoiding using the page lock.
---
include/linux/balloon_compaction.h | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-)
include/linux/balloon_compaction.h renamed from include/linux/balloon_compaction.h~mm-balloon_compaction-movable_ops-doc-updates +6 -7
@@ -4,12 +4,13 @@* * Common interface definitions for making balloon pages movable by compaction. * -* Balloon page migration makes use of the general non-lru movable page +* Balloon page migration makes use of the general "movable_ops page migration" * feature. * * page->private is used to reference the responsible balloon device. -* page->mapping is used in context of non-lru page migration to reference -* the address space operations for page isolation/migration/compaction. +* That these pages have movable_ops, and which movable_ops apply, +* is derived from the page type (PageOffline()) combined with the +* PG_movable_ops flag (PageMovableOps()). * * As the page isolation scanning step a compaction thread does is a lockless * procedure (from a page standpoint), it might bring some racy situations while
@@ -17,12 +18,10 @@* and safely perform balloon's page compaction and migration we must, always, * ensure following these simple rules: * -* i. when updating a balloon's page ->mapping element, strictly do it under -* the following lock order, independently of the far superior -* locking scheme (lru_lock, balloon_lock): +* i. Setting the PG_movable_ops flag and page->private with the following +* lock order * +-page_lock(page); * +--spin_lock_irq(&b_dev_info->pages_lock); -* ... page->mapping updates here ... * * ii. isolation or dequeueing procedure must remove the page from balloon * device page list under b_dev_info->pages_lock.
_
Patches currently in -mm which might be from [email protected] are
mm-convert-fpb_ignore_-into-fpb_respect_.patch mm-smaller-folio_pte_batch-improvements.patch mm-split-folio_pte_batch-into-folio_pte_batch-and-folio_pte_batch_flags.patch mm-remove-boolean-output-parameters-from-folio_pte_batch_ext.patch mm-memory-introduce-is_huge_zero_pfn-and-use-it-in-vm_normal_page_pmd.patch