KVM: selftests: Stop passing a memslot to nested_map_memslot()

Browse source

On x86, KVM selftests use memslot 0 for all the default regions used by
the test infrastructure. This is an implementation detail.
nested_map_memslot() is currently used to map the default regions by
explicitly passing slot 0, which leaks the library implementation into
the caller.

Rename the function to a very verbose
nested_identity_map_default_memslots() to reflect what it actually does.
Add an assertion that only memslot 0 is being used so that the
implementation does not change from under us.

No functional change intended.

Signed-off-by: Yosry Ahmed <yosry.ahmed@linux.dev>
Link: https://patch.msgid.link/20251230230150.4150236-3-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>

...

This commit is contained in:

Yosry Ahmed 2025-12-30 15:01:31 -08:00 • committed by Sean Christopherson

parent 69e81ed5e6

commit 97dfbdfea4

3 changed files with 11 additions and 7 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

4

tools/testing/selftests/kvm/include/x86/vmx.h

View file

12

tools/testing/selftests/kvm/lib/x86/vmx.c

View file

2

tools/testing/selftests/kvm/x86/vmx_dirty_log_test.c

View file