summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorIlia Levi <ilia.levi@intel.com>2026-09-08 17:50:48 +0100
committerRodrigo Vivi <rodrigo.vivi@intel.com>2026-09-14 08:48:53 -0400
commit247a82da6f563dcfd9074a68f99a0c0997d0679c (patch)
treef7e044204a235dc99942a25b7ab866fc38795f14 /tools/perf/scripts/python/bin
parentfd73f4a6659897191fa0d40695fe370925dd3780 (diff)
downloadlinux-next-247a82da6f563dcfd9074a68f99a0c0997d0679c.tar.gz
linux-next-247a82da6f563dcfd9074a68f99a0c0997d0679c.zip
drm/xe/mmio_gem: forbid VMA split
The fault handler assumes it always operates on a VMA spanning the entire GEM object. This does not hold when the VMA has been split, e.g. by a partial munmap or mprotect. In that case the handler may map wrong physical pages or cause SIGBUS. Handle this by forbidding VMA split, as partial unmaps are not deemed useful for MMIO GEMs. Suggested-by: Matthew Auld <matthew.auld@intel.com> Signed-off-by: Ilia Levi <ilia.levi@intel.com> Fixes: 1ffcf8b8ae8a ("drm/xe: Support for mmap-ing mmio regions") Reviewed-by: Matthew Auld <matthew.auld@intel.com> Signed-off-by: Matthew Auld <matthew.auld@intel.com> Link: https://patch.msgid.link/20260908165046.1393557-11-matthew.auld@intel.com (cherry picked from commit f3391a0b12d7bf826a0b21600d2f294f3dce4c14) Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions