diff options
author | David Hildenbrand <[email protected]> | 2017-11-10 16:18:05 +0100 |
---|---|---|
committer | Christian Borntraeger <[email protected]> | 2018-01-16 16:15:16 +0100 |
commit | 9696594158ec43d210137c1b93313efde8f7315a (patch) | |
tree | b4f5560a0794b59a90cc2e060651a13f64077072 /tools/perf/scripts/python/call-graph-from-sql.py | |
parent | 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36 (diff) |
s390x/mm: cleanup gmap_pte_op_walk()
gmap_mprotect_notify() refuses shadow gmaps. Turns out that
a) gmap_protect_range()
b) gmap_read_table()
c) gmap_pte_op_walk()
Are never called for gmap shadows. And never should be. This dates back
to gmap shadow prototypes where we allowed to call mprotect_notify() on
the gmap shadow (to get notified about the prefix pages getting removed).
This is avoided by always getting notified about any change on the gmap
shadow.
The only real function for walking page tables on shadow gmaps is
gmap_table_walk().
So, essentially, these functions should never get called and
gmap_pte_op_walk() can be cleaned up. Add some checks to callers of
gmap_pte_op_walk().
Signed-off-by: David Hildenbrand <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Janosch Frank <[email protected]>
Acked-by: Cornelia Huck <[email protected]>
Signed-off-by: Christian Borntraeger <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions