summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorChen-Yu Tsai <wenst@chromium.org>2026-03-17 12:00:32 +0800
committerChen-Yu Tsai <wenst@chromium.org>2026-03-26 14:35:18 +0800
commite3eb0e70815cc02ea15298818e37d8b0a0930ab1 (patch)
tree8d71003f33b8ed41886d31e0c8065180ed9a192c /tools/perf/scripts/python/stackcollapse.py
parent1f513a3ec3a945efb30c963681ac32ac7b99928b (diff)
drm/gem-dma: set VM_DONTDUMP for mmap
When the mmap function was converted from a file op to a GEM object function in commit f5ca8eb6f9bd ("drm/cma-helper: Implement mmap as GEM CMA object functions") some VM flags were not lifted from drm_gem_mmap(): - VM_IO - VM_DONTEXPAND - VM_DONTDUMP VM_DONTEXPAND was added back in commit 59f39bfa6553 ("drm/cma-helper: Set VM_DONTEXPAND for mmap"). VM_IO doesn't make sense since these are memory buffers, while "IO tells people not to look at these pages (accesses can have side effects)". Add back VM_DONTDUMP. This matches the behavior of most other GEM implementations. Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de> Link: https://patch.msgid.link/20260317040034.617585-1-wenst@chromium.org Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions