From 090a7f1009b8447565a03b649189e6ff83e8e5e7 Mon Sep 17 00:00:00 2001 From: Marco Pagani Date: Fri, 25 Aug 2023 15:35:46 +0200 Subject: [PATCH] docs/mm: remove references to hmm_mirror ops and clean typos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Clean typos and remove the reference to the sync_cpu_device_pagetables() callback since all hmm_mirror ops have been removed. Fixes: a22dd506400d ("mm/hmm: remove hmm_mirror and related") Signed-off-by: Marco Pagani Reviewed-by: Mika Penttilä Reviewed-by: Jason Gunthorpe Signed-off-by: Jonathan Corbet Link: https://lore.kernel.org/r/20230825133546.249683-1-marpagan@redhat.com --- Documentation/mm/hmm.rst | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/Documentation/mm/hmm.rst b/Documentation/mm/hmm.rst index fec21e6f2284..0595098a74d9 100644 --- a/Documentation/mm/hmm.rst +++ b/Documentation/mm/hmm.rst @@ -163,16 +163,7 @@ use:: It will trigger a page fault on missing or read-only entries if write access is requested (see below). Page faults use the generic mm page fault code path just -like a CPU page fault. - -Both functions copy CPU page table entries into their pfns array argument. Each -entry in that array corresponds to an address in the virtual range. HMM -provides a set of flags to help the driver identify special CPU page table -entries. - -Locking within the sync_cpu_device_pagetables() callback is the most important -aspect the driver must respect in order to keep things properly synchronized. -The usage pattern is:: +like a CPU page fault. The usage pattern is:: int driver_populate_range(...) {