Thread (36 messages) 36 messages, 9 authors, 2024-11-15
STALE577d
Revisions (2)
  1. v3 current
  2. v4 [diff vs current]

[RFC PATCH v3 5/6] kvm: document KVM_GMEM_NO_DIRECT_MAP flag

From: Patrick Roy <hidden>
Date: 2024-10-30 13:50:38
Also in: kvm, linux-doc, linux-kselftest, linux-mm, linux-riscv, linux-s390, lkml, loongarch
Subsystem: documentation, kernel virtual machine (kvm), the rest · Maintainers: Jonathan Corbet, Paolo Bonzini, Linus Torvalds

Signed-off-by: Patrick Roy <redacted>
---
 Documentation/virt/kvm/api.rst | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
index edc070c6e19b2..c8e21c523411c 100644
--- a/Documentation/virt/kvm/api.rst
+++ b/Documentation/virt/kvm/api.rst
@@ -6382,6 +6382,20 @@ a single guest_memfd file, but the bound ranges must not overlap).
 
 See KVM_SET_USER_MEMORY_REGION2 for additional details.
 
+The following flags are defined:
+
+KVM_GMEM_NO_DIRECT_MAP
+   Ensure memory backing this guest_memfd inode is unmapped from the kernel's
+   address space.
+
+Errors:
+
+  ========== ===============================================================
+  EOPNOTSUPP `KVM_GMEM_NO_DIRECT_MAP` was set in `flags`, but the host does
+             not support direct map manipulations.
+  ========== ===============================================================
+
+
 4.143 KVM_PRE_FAULT_MEMORY
 ---------------------------
 
-- 
2.47.0
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help