diff options
| author | David Hildenbrand <david@redhat.com> | 2022-11-16 11:26:46 +0100 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2022-11-30 15:58:58 -0800 |
| commit | aea06577a9005ca81c35196d6171cac346d3b251 (patch) | |
| tree | 4b85baac7d202c287e6d66da5b2b8f45761ec79f /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | mm: rework handling in do_wp_page() based on private vs. shared mappings (diff) | |
| download | linux-aea06577a9005ca81c35196d6171cac346d3b251.tar.gz linux-aea06577a9005ca81c35196d6171cac346d3b251.zip | |
mm: don't call vm_ops->huge_fault() in wp_huge_pmd()/wp_huge_pud() for private mappings
If we already have a PMD/PUD mapped write-protected in a private mapping
and we want to break COW either due to FAULT_FLAG_WRITE or
FAULT_FLAG_UNSHARE, there is no need to inform the file system just like on
the PTE path.
Let's just split (->zap) + fallback in that case.
This is a preparation for more generic FAULT_FLAG_UNSHARE support in
COW mappings.
Link: https://lkml.kernel.org/r/20221116102659.70287-8-david@redhat.com
Signed-off-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions