From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, "David Hildenbrand" <david@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Alistair Popple" <apopple@nvidia.com>,
"Jason Gunthorpe" <jgg@nvidia.com>
Subject: [PATCH v2 0/5] mm: cleanups for device-exclusive entries (hmm)
Date: Wed, 26 Feb 2025 14:22:52 +0100 [thread overview]
Message-ID: <20250226132257.2826043-1-david@redhat.com> (raw)
Based on mm/mm-unstable, which already contains [1].
Some smaller device-exclusive cleanups I have lying around. Tested
using the hmm selftests without surprises.
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: "Jérôme Glisse" <jglisse@redhat.com>
Cc: Simona Vetter <simona@ffwll.ch>
Cc: Alistair Popple <apopple@nvidia.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>
v1 -> v2:
* Rebased on top of [1]
* "mm/memory: remove PageAnonExclusive sanity-check in
restore_exclusive_pte()"
-> Added
* "mm/memory: document restore_exclusive_pte()"
-> adjust/clarify/simplify documentation
* "mm/mmu_notifier: use MMU_NOTIFY_CLEAR in
remove_device_exclusive_entry()"
-> Use MMU_NOTIFY_EXCLUSIVE only for a single purpose such that we
always have the owner
[1] https://lkml.kernel.org/r/20250210193801.781278-1-david@redhat.com
David Hildenbrand (5):
lib/test_hmm: make dmirror_atomic_map() consume a single page
mm/memory: remove PageAnonExclusive sanity-check in
restore_exclusive_pte()
mm/memory: pass folio and pte to restore_exclusive_pte()
mm/memory: document restore_exclusive_pte()
mm/mmu_notifier: use MMU_NOTIFY_CLEAR in
remove_device_exclusive_entry()
include/linux/mmu_notifier.h | 8 ++---
lib/test_hmm.c | 32 ++++++-------------
mm/memory.c | 60 ++++++++++++++++++++++++------------
3 files changed, 55 insertions(+), 45 deletions(-)
base-commit: 598d34afeca6bb10554846cf157a3ded8729516c
--
2.48.1
next reply other threads:[~2025-02-26 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 13:22 David Hildenbrand [this message]
2025-02-26 13:22 ` [PATCH v2 1/5] lib/test_hmm: make dmirror_atomic_map() consume a single page David Hildenbrand
2025-02-26 13:22 ` [PATCH v2 2/5] mm/memory: remove PageAnonExclusive sanity-check in restore_exclusive_pte() David Hildenbrand
2025-02-26 13:22 ` [PATCH v2 3/5] mm/memory: pass folio and pte to restore_exclusive_pte() David Hildenbrand
2025-02-26 13:22 ` [PATCH v2 4/5] mm/memory: document restore_exclusive_pte() David Hildenbrand
2025-02-26 13:22 ` [PATCH v2 5/5] mm/mmu_notifier: use MMU_NOTIFY_CLEAR in remove_device_exclusive_entry() David Hildenbrand
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=20250226132257.2826043-1-david@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=jgg@nvidia.com \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=simona@ffwll.ch \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox