diff options
author | Peter Collingbourne <[email protected]> | 2022-11-03 18:10:41 -0700 |
---|---|---|
committer | Marc Zyngier <[email protected]> | 2022-11-29 09:26:07 +0000 |
commit | a4baf8d2639f24d4d31983ff67c01878e7a5393f (patch) | |
tree | 65133fd8a6e2f143506fe64fc314fa102345cb51 | |
parent | c911f0d4687947915f04024aa01803247fcf7f1a (diff) |
Documentation: document the ABI changes for KVM_CAP_ARM_MTE
Document both the restriction on VM_MTE_ALLOWED mappings and
the relaxation for shared mappings.
Signed-off-by: Peter Collingbourne <[email protected]>
Acked-by: Catalin Marinas <[email protected]>
Reviewed-by: Cornelia Huck <[email protected]>
Signed-off-by: Marc Zyngier <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
-rw-r--r-- | Documentation/virt/kvm/api.rst | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst index eee9f857a986..b55f80dadcfe 100644 --- a/Documentation/virt/kvm/api.rst +++ b/Documentation/virt/kvm/api.rst @@ -7385,8 +7385,9 @@ hibernation of the host; however the VMM needs to manually save/restore the tags as appropriate if the VM is migrated. When this capability is enabled all memory in memslots must be mapped as -not-shareable (no MAP_SHARED), attempts to create a memslot with a -MAP_SHARED mmap will result in an -EINVAL return. +``MAP_ANONYMOUS`` or with a RAM-based file mapping (``tmpfs``, ``memfd``), +attempts to create a memslot with an invalid mmap will result in an +-EINVAL return. When enabled the VMM may make use of the ``KVM_ARM_MTE_COPY_TAGS`` ioctl to perform a bulk copy of tags to/from the guest. |