mirror of
https://github.com/torvalds/linux.git
synced 2026-07-31 19:47:08 +02:00
mm/mmu_notifier: fix a begin vs. start typo in the invalidate range comment
Fix a goof in the block comment for invalidate_range_{start,end}() where
start() is incorrectly referred to as begin().
No functional change intended.
[seanjc@google.com: split to separate patch, write changelog]
Link: https://lore.kernel.org/20260513163546.1176742-1-seanjc@google.com
Signed-off-by: Takahiro Itazuri <itazur@amazon.com>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: David Hildenbrand (Arm) <david@kernel.org>
Reviewed-by: Lorenzo Stoakes <ljs@kernel.org>
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Cc: Liam R. Howlett <liam@infradead.org>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Vlastimil Babka <vbabka@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
This commit is contained in:
parent
fb95c50921
commit
80eacd489a
|
|
@ -134,8 +134,8 @@ struct mmu_notifier_ops {
|
|||
* Invalidation of multiple concurrent ranges may be
|
||||
* optionally permitted by the driver. Either way the
|
||||
* establishment of sptes is forbidden in the range passed to
|
||||
* invalidate_range_begin/end for the whole duration of the
|
||||
* invalidate_range_begin/end critical section.
|
||||
* invalidate_range_start/end for the whole duration of the
|
||||
* invalidate_range_start/end critical section.
|
||||
*
|
||||
* invalidate_range_start() is called when all pages in the
|
||||
* range are still mapped and have at least a refcount of one.
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user