mm-mmu_notifier-use-mmu_notify_clear-in-remove_device_exclusive_entry.patch removed from -mm tree
The quilt patch titled
Subject: mm/mmu_notifier: use MMU_NOTIFY_CLEAR in remove_device_exclusive_entry()
has been removed from the -mm tree. Its filename was
mm-mmu_notifier-use-mmu_notify_clear-in-remove_device_exclusive_entry.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/mmu_notifier: use MMU_NOTIFY_CLEAR in remove_device_exclusive_entry()
Date: Wed, 26 Feb 2025 14:22:57 +0100
Let's limit the use of MMU_NOTIFY_EXCLUSIVE to the case where we convert a present PTE to device-exclusive. For the other case, we can simply use MMU_NOTIFY_CLEAR, because it really is clearing the device-exclusive entry first, to then install the present entry.
Update the documentation of MMU_NOTIFY_EXCLUSIVE, to document the single use case more thoroughly.
If ever required, we could add a separate MMU_NOTIFY_CLEAR_EXCLUSIVE; for now using MMU_NOTIFY_CLEAR seems to be sufficient.
---
include/linux/mmu_notifier.h | 8 ++++---- mm/memory.c | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-)
include/linux/mmu_notifier.h renamed from include/linux/mmu_notifier.h~mm-mmu_notifier-use-mmu_notify_clear-in-remove_device_exclusive_entry +4 -4
@@ -43,10 +43,10 @@ struct mmu_interval_notifier;* a device driver to possibly ignore the invalidation if the * owner field matches the driver's device private pgmap owner. * -* @MMU_NOTIFY_EXCLUSIVE: to signal a device driver that the device will no -* longer have exclusive access to the page. When sent during creation of an -* exclusive range the owner will be initialised to the value provided by the -* caller of make_device_exclusive(), otherwise the owner will be NULL. +* @MMU_NOTIFY_EXCLUSIVE: conversion of a page table entry to device-exclusive. +* The owner is initialized to the value provided by the caller of +* make_device_exclusive(), such that this caller can filter out these +* events. */ enum mmu_notifier_event {MMU_NOTIFY_UNMAP =0 ,
mm/memory.c renamed from mm/memory.c~mm-mmu_notifier-use-mmu_notify_clear-in-remove_device_exclusive_entry +1 -1
@@ -4003,7 +4003,7 @@ static vm_fault_t remove_device_exclusivfolio_put (folio);return ret; } -mmu_notifier_range_init_owner (&range,MMU_NOTIFY_EXCLUSIVE ,0 , +mmu_notifier_range_init_owner (&range,MMU_NOTIFY_CLEAR ,0 , vma->vm_mm, vmf->address &PAGE_MASK , (vmf->address &PAGE_MASK ) +PAGE_SIZE ,NULL );mmu_notifier_invalidate_range_start (&range);
_
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