diff options
| author | Ackerley Tng <ackerleytng@google.com> | 2026-09-10 16:56:00 -0700 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2026-09-22 07:28:42 -0700 |
| commit | bfb9b5a286ea6a190bfed191de3a6b6f0bf801c4 (patch) | |
| tree | f6074c496c46bad4eebfab691f9537d9a364d41e /tools/perf/scripts/python/stackcollapse.py | |
| parent | 5362c5fb88f6df1a00eda33ab8487ce09ebdb71a (diff) | |
KVM: selftests: Test that truncation does not change shared/private status
Add a test to verify that deallocating a page in a guest memfd region via
fallocate() with FALLOC_FL_PUNCH_HOLE does not alter the shared or private
status of the corresponding memory range.
When a page backing a guest memfd mapping is deallocated, e.g., by punching
a hole or truncating the file, and then subsequently faulted back in, the
new page must inherit the correct shared/private status tracked by
guest_memfd.
Co-developed-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Ackerley Tng <ackerleytng@google.com>
Tested-by: Shivank Garg <shivankg@amd.com>
Reviewed-by: Fuad Tabba <tabba@google.com>
Tested-by: Yan Zhao <yan.y.zhao@intel.com>
Link: https://patch.msgid.link/20260910-gmem-inplace-conversion-v13-34-dd6fbf94f4e1@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions