diff options
author | 2018-08-06 17:54:07 +0200 | |
---|---|---|
committer | 2018-10-01 08:52:24 +0200 | |
commit | af4bf6c3d9b45b62da86d928d3fd2d4ddc8549e6 (patch) | |
tree | 80ed16c57af5bb4ae68a1f12c6977143114ed186 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | KVM: s390: set host program identifier (diff) | |
download | linux-dev-af4bf6c3d9b45b62da86d928d3fd2d4ddc8549e6.tar.xz linux-dev-af4bf6c3d9b45b62da86d928d3fd2d4ddc8549e6.zip |
s390/mm: optimize locking without huge pages in gmap_pmd_op_walk()
Right now we temporarily take the page table lock in
gmap_pmd_op_walk() even though we know we won't need it (if we can
never have 1mb pages mapped into the gmap).
Let's make this a special case, so gmap_protect_range() and
gmap_sync_dirty_log_pmd() will not take the lock when huge pages are
not allowed.
gmap_protect_range() is called quite frequently for managing shadow
page tables in vSIE environments.
Signed-off-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
Message-Id: <20180806155407.15252-1-david@redhat.com>
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions