Add missing commas after "e.g." and "i.e." in the KVM API documentation to improve readability and follow standard punctuation usage. Signed-off-by: Afkari Zergaw --- Documentation/virt/kvm/api.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst index fc5736839edd..c8500f0e913a 100644 --- a/Documentation/virt/kvm/api.rst +++ b/Documentation/virt/kvm/api.rst @@ -6346,12 +6346,12 @@ A KVM_MEM_GUEST_MEMFD region _must_ have a valid guest_memfd (private memory) an userspace_addr (shared memory). However, "valid" for userspace_addr simply means that the address itself must be a legal userspace address. The backing mapping for userspace_addr is not required to be valid/populated at the time of -KVM_SET_USER_MEMORY_REGION2, e.g. shared memory can be lazily mapped/allocated +KVM_SET_USER_MEMORY_REGION2, e.g., shared memory can be lazily mapped/allocated on-demand. -When mapping a gfn into the guest, KVM selects shared vs. private, i.e consumes +When mapping a gfn into the guest, KVM selects shared vs. private, i.e., consumes userspace_addr vs. guest_memfd, based on the gfn's KVM_MEMORY_ATTRIBUTE_PRIVATE -state. At VM creation time, all memory is shared, i.e. the PRIVATE attribute +state. At VM creation time, all memory is shared, i.e., the PRIVATE attribute is '0' for all gfns. Userspace can control whether memory is shared/private by toggling KVM_MEMORY_ATTRIBUTE_PRIVATE via KVM_SET_MEMORY_ATTRIBUTES as needed. -- 2.43.0