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

From: Joerg Roedel
Date: Tue Oct 28 2014 - 13:14:31 EST


From: Joerg Roedel <jroedel@xxxxxxx>

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(-)

--
1.8.4.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/