mm-memory-document-restore_exclusive_pte.patch removed from -mm tree
The quilt patch titled
Subject: mm/memory: document restore_exclusive_pte()
has been removed from the -mm tree. Its filename was
mm-memory-document-restore_exclusive_pte.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/memory: document restore_exclusive_pte()
Date: Wed, 26 Feb 2025 14:22:56 +0100
Let's document how this function is to be used, and why the folio lock is involved.
---
mm/memory.c | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+)
mm/memory.c renamed from mm/memory.c~mm-memory-document-restore_exclusive_pte +26 -0
@@ -716,6 +716,32 @@ struct folio *vm_normal_folio_pmd(struct }#endif +/** +* restore_exclusive_pte - Restore a device-exclusive entry +* @vma: VMA covering @address +* @folio: the mapped folio +* @page: the mapped folio page +* @address: the virtual address +* @ptep: pte pointer into the locked page table mapping the folio page +* @orig_pte: pte value at @ptep +* +* Restore a device-exclusive non-swap entry to an ordinary present pte. +* +* The folio and the page table must be locked, and MMU notifiers must have +* been called to invalidate any (exclusive) device mappings. +* +* Locking the folio makes sure that anybody who just converted the pte to +* a device-exclusive entry can map it into the device to make forward +* progress without others converting it back until the folio was unlocked. +* +* If the folio lock ever becomes an issue, we can stop relying on the folio +* lock; it might make some scenarios with heavy thrashing less likely to +* make forward progress, but these scenarios might not be valid use cases. +* +* Note that the folio lock does not protect against all cases of concurrent +* page table modifications (e.g., MADV_DONTNEED, mprotect), so device drivers +* must use MMU notifiers to sync against any concurrent changes. +*/ static void restore_exclusive_pte (struct vm_area_struct *vma,struct folio *folio,struct page *page,unsigned long address,pte_t *ptep,pte_t orig_pte)
_
Patches currently in -mm which might be from [email protected] are
mm-factor-out-large-folio-handling-from-folio_order-into-folio_large_order.patch mm-factor-out-large-folio-handling-from-folio_nr_pages-into-folio_large_nr_pages.patch mm-let-_folio_nr_pages-overlay-memcg_data-in-first-tail-page.patch mm-let-_folio_nr_pages-overlay-memcg_data-in-first-tail-page-fix.patch mm-move-hugetlb-specific-things-in-folio-to-page.patch mm-move-_pincount-in-folio-to-page-on-32bit.patch mm-move-_entire_mapcount-in-folio-to-page-on-32bit.patch mm-rmap-pass-dst_vma-to-folio_dup_file_rmap_pte-and-friends.patch mm-rmap-pass-vma-to-__folio_add_rmap.patch mm-rmap-abstract-large-mapcount-operations-for-large-folios-hugetlb.patch bit_spinlock-__always_inline-unlock-functions.patch mm-rmap-use-folio_large_nr_pages-in-add-remove-functions.patch mm-rmap-basic-mm-owner-tracking-for-large-folios-hugetlb.patch mm-copy-on-write-cow-reuse-support-for-pte-mapped-thp.patch mm-convert-folio_likely_mapped_shared-to-folio_maybe_mapped_shared.patch mm-config_no_page_mapcount-to-prepare-for-not-maintain-per-page-mapcounts-in-large-folios.patch fs-proc-page-remove-per-page-mapcount-dependency-for-proc-kpagecount-config_no_page_mapcount.patch fs-proc-task_mmu-remove-per-page-mapcount-dependency-for-pm_mmap_exclusive-config_no_page_mapcount.patch fs-proc-task_mmu-remove-per-page-mapcount-dependency-for-mapmax-config_no_page_mapcount.patch fs-proc-task_mmu-remove-per-page-mapcount-dependency-for-smaps-smaps_rollup-config_no_page_mapcount.patch mm-stop-maintaining-the-per-page-mapcount-of-large-folios-config_no_page_mapcount.patch