From: Albert Esteve <aesteve@redhat.com>
To: qemu-devel@nongnu.org
Cc: slp@redhat.com, hi@alyssa.is, mst@redhat.com,
stefanha@redhat.com, Stefano Garzarella <sgarzare@redhat.com>,
david@redhat.com, stevensd@chromium.org, jasowang@redhat.com,
Albert Esteve <aesteve@redhat.com>
Subject: [PATCH 1/3] vhost_user.rst: Add SHMEM_MAP/_UNMAP to spec
Date: Thu, 12 Sep 2024 16:44:30 +0200 [thread overview]
Message-ID: <20240912144432.126717-2-aesteve@redhat.com> (raw)
In-Reply-To: <20240912144432.126717-1-aesteve@redhat.com>
Add SHMEM_MAP/_UNMAP request to the vhost-user
spec documentation.
Signed-off-by: Albert Esteve <aesteve@redhat.com>
---
docs/interop/vhost-user.rst | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/docs/interop/vhost-user.rst b/docs/interop/vhost-user.rst
index d8419fd2f1..d680fea4a3 100644
--- a/docs/interop/vhost-user.rst
+++ b/docs/interop/vhost-user.rst
@@ -369,6 +369,7 @@ In QEMU the vhost-user message is implemented with the following struct:
VhostUserConfig config;
VhostUserVringArea area;
VhostUserInflight inflight;
+ VhostUserMMap mmap;
};
} QEMU_PACKED VhostUserMsg;
@@ -1859,6 +1860,36 @@ is sent by the front-end.
when the operation is successful, or non-zero otherwise. Note that if the
operation fails, no fd is sent to the backend.
+``VHOST_USER_BACKEND_SHMEM_MAP``
+ :id: 9
+ :equivalent ioctl: N/A
+ :request payload: fd and ``struct VhostUserMMap``
+ :reply payload: N/A
+
+ This message can be submitted by the backends to advertise a new mapping
+ to be made in a given VIRTIO Shared Memory Region. Upon receiving the message,
+ The front-end will mmap the given fd into the VIRTIO Shared Memory Region
+ with the requested ``shmid``. A reply is generated indicating whether mapping
+ succeeded.
+
+ Mapping over an already existing map is not allowed and request shall fail.
+ Therefore, the memory range in the request must correspond with a valid,
+ free region of the VIRTIO Shared Memory Region. Also, note that mappings
+ consume resources and that the request can fail when there are no resources
+ available.
+
+``VHOST_USER_BACKEND_SHMEM_UNMAP``
+ :id: 10
+ :equivalent ioctl: N/A
+ :request payload: ``struct VhostUserMMap``
+ :reply payload: N/A
+
+ This message can be submitted by the backends so that the front-end un-mmap
+ a given range (``shm_offset``, ``len``) in the VIRTIO Shared Memory Region
+ with the requested ``shmid``. Note that the given range shall correspond to
+ the entirety of a valid mapped region.
+ A reply is generated indicating whether unmapping succeeded.
+
.. _reply_ack:
VHOST_USER_PROTOCOL_F_REPLY_ACK
--
2.45.2
next prev parent reply other threads:[~2024-09-12 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 14:44 [PATCH 0/3] Document SHMEM vhost-user requests Albert Esteve
2024-09-12 14:44 ` Albert Esteve [this message]
2024-09-16 16:29 ` [PATCH 1/3] vhost_user.rst: Add SHMEM_MAP/_UNMAP to spec Stefan Hajnoczi
2024-09-16 16:35 ` Stefan Hajnoczi
2024-09-12 14:44 ` [PATCH 2/3] vhost_user.rst: Align VhostUserMsg excerpt members Albert Esteve
2024-09-12 14:44 ` [PATCH 3/3] vhost_user.rst: Add GET_SHMEM_CONFIG message Albert Esteve
2024-09-12 16:42 ` Alyssa Ross
2024-09-16 16:34 ` Stefan Hajnoczi
2024-09-12 14:57 ` [PATCH 0/3] Document SHMEM vhost-user requests Albert Esteve
2024-09-16 16:55 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240912144432.126717-2-aesteve@redhat.com \
--to=aesteve@redhat.com \
--cc=david@redhat.com \
--cc=hi@alyssa.is \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=slp@redhat.com \
--cc=stefanha@redhat.com \
--cc=stevensd@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).