diff options
author | Dan Williams <[email protected]> | 2018-12-04 13:37:16 -0800 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2018-12-05 09:03:06 +0100 |
commit | 4369deaa2f022ef92da45a0e7eec8a4a52e8e8a4 (patch) | |
tree | 6732d7f5dd26688e96eaf9d93fd406cadf54e8c8 /tools/perf/scripts/python/stackcollapse.py | |
parent | 0cebbb60f759a709dabb3c87b9704f9844878850 (diff) |
generic/pgtable: Introduce set_pte_safe()
Commit:
f77084d96355 "x86/mm/pat: Disable preemption around __flush_tlb_all()"
introduced a warning to capture cases __flush_tlb_all() is called without
pre-emption disabled. It triggers a false positive warning in the memory
hotplug path.
On investigation it was found that the __flush_tlb_all() calls are not
necessary. However, they are only "not necessary" in practice provided
the ptes are being initially populated from the !present state.
Introduce set_pte_safe() as a sanity check that the pte is being updated
in a way that does not require a TLB flush.
Forgive the macro, the availability of the various of set_pte() levels
is hit and miss across architectures.
[ mingo: Minor readability edits. ]
Suggested-by: Peter Zijlstra <[email protected]>
Suggested-by: Dave Hansen <[email protected]>
Signed-off-by: Dan Williams <[email protected]>
Acked-by: Peter Zijlstra (Intel) <[email protected]>
Acked-by: Kirill A. Shutemov <[email protected]>
Cc: Andy Lutomirski <[email protected]>
Cc: Borislav Petkov <[email protected]>
Cc: Dave Hansen <[email protected]>
Cc: H. Peter Anvin <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Rik van Riel <[email protected]>
Cc: Sebastian Andrzej Siewior <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions