Skip to content

mmu_notifier: Allow to manage CPU external TLBs

Joerg Roedel linux-iommu linux-mm lkml 4 versions – New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v4 Latest3 patches 0 repliesNew
  2. v33 patches 9 repliesSuperseded
  3. v23 patches 2 repliesSuperseded
Earlier versions · 1
VersionPostedPatchesRepliesStatus
v13 patches10 repliesSuperseded

Changes in v4 from the cover letter

* Rebased to v3.18-rc2
* Updated patch description and some comments

Patches in v4 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3mmu_notifier: Add mmu_notifier_invalidate_range()include/linux/mmu_notifier.h+10 -00 replies
2/3mmu_notifier: Call mmu_notifier_invalidate_range() from VMMinclude/linux/mmu_notifier.h kernel/events/uprobes.c mm/fremap.c +6 more+61 -120 replies
3/3mmu_notifier: Add the call-back for mmu_notifier_invalidate_range()include/linux/mmu_notifier.h mm/mmu_notifier.c+57 -50 replies

Reviews trailers per patch

All 3 patches have a Reviewed-by or Acked-by.

PatchAndrea ArcangeliJérôme Glisse
1/3R-b R-b
2/3R-b R-b
3/3R-b R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v4 thread

Cover letter [PATCH 0/3 v4] mmu_notifier: Allow to manage CPU external TLBs

From: Joerg Roedel <[email protected]>

Changes V3->V4:

* Rebased to v3.18-rc2
* Updated patch description and some comments

Changes V2->V3:

* Rebased to v3.17-rc4
* Fixed compile error because pmdp_get_and_clear_notify was missing

Changes V1->V2:

* Rebase to v3.16-rc7
* Added call of ->invalidate_range to __mmu_notifier_invalidate_end() so that the subsystem doesn't need to register an ->invalidate_end() call-back, subsystems will likely either register invalidate_range_start/end or invalidate_range, so that should be fine.
* Re-orded declarations a bit to reflect that invalidate_range is not only called between invalidate_range_start/end
* Updated documentation to cover the case where invalidate_range is called outside of invalidate_range_start/end to flush page-table pages out of the TLB

Hi,

here is v4 of my patch-set which extends the mmu-notifiers to allow managing CPU external TLBs. A more in-depth description on the How and Why of this patch-set can be found in the description of patch 1/3.

Any comments and review appreciated!

Thanks,

Joerg

Joerg Roedel (3):
mmu_notifier: Add mmu_notifier_invalidate_range()
mmu_notifier: Call mmu_notifier_invalidate_range() from VMM
mmu_notifier: Add the call-back for mmu_notifier_invalidate_range()

 include/linux/mmu_notifier.h | 88 +++++++++++++++++++++++++++++++++++++++++---
 kernel/events/uprobes.c      |  2 +-
 mm/fremap.c                  |  2 +-
 mm/huge_memory.c             |  9 +++--
 mm/hugetlb.c                 |  7 +++-
 mm/ksm.c                     |  4 +-
 mm/memory.c                  |  3 +-
 mm/migrate.c                 |  3 +-
 mm/mmu_notifier.c            | 25 +++++++++++++
 mm/rmap.c                    |  2 +-
 10 files changed, 128 insertions(+), 17 deletions(-)
Signature · 7 lines
1.8.4.5

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to [email protected].  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>