qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Albert Esteve <aesteve@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	"Fabiano Rosas" <farosas@suse.de>,
	hi@alyssa.is, "Alex Bennée" <alex.bennee@linaro.org>,
	"Laurent Vivier" <lvivier@redhat.com>,
	slp@redhat.com, "Stefano Garzarella" <sgarzare@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	david@redhat.com, jasowang@redhat.com, stefanha@redhat.com,
	dbassey@redhat.com, stevensd@chromium.org,
	"Albert Esteve" <aesteve@redhat.com>
Subject: [PATCH v6 2/8] vhost_user.rst: Align VhostUserMsg excerpt members
Date: Thu, 14 Aug 2025 10:37:43 +0200	[thread overview]
Message-ID: <20250814083749.1317197-3-aesteve@redhat.com> (raw)
In-Reply-To: <20250814083749.1317197-1-aesteve@redhat.com>

Add missing members to the VhostUserMsg excerpt in
the vhost-user spec documentation.

Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Albert Esteve <aesteve@redhat.com>
---
 docs/interop/vhost-user.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/interop/vhost-user.rst b/docs/interop/vhost-user.rst
index 2e50f2ddfa..436a94c0ee 100644
--- a/docs/interop/vhost-user.rst
+++ b/docs/interop/vhost-user.rst
@@ -366,11 +366,15 @@ In QEMU the vhost-user message is implemented with the following struct:
           struct vhost_vring_state state;
           struct vhost_vring_addr addr;
           VhostUserMemory memory;
+          VhostUserMemRegMsg mem_reg;
           VhostUserLog log;
           struct vhost_iotlb_msg iotlb;
           VhostUserConfig config;
+          VhostUserCryptoSession session;
           VhostUserVringArea area;
           VhostUserInflight inflight;
+          VhostUserShared object;
+          VhostUserTransferDeviceState transfer_state;
       };
   } QEMU_PACKED VhostUserMsg;
 
-- 
2.49.0



  parent reply	other threads:[~2025-08-14  8:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14  8:37 [PATCH v6 0/8] vhost-user: Add SHMEM_MAP/UNMAP requests Albert Esteve
2025-08-14  8:37 ` [PATCH v6 1/8] vhost-user: Add VirtIO Shared Memory map request Albert Esteve
2025-08-18  7:05   ` Albert Esteve
2025-08-18  7:37   ` David Hildenbrand
2025-08-18  8:51     ` Albert Esteve
2025-08-14  8:37 ` Albert Esteve [this message]
2025-08-14  8:37 ` [PATCH v6 3/8] vhost_user.rst: Add SHMEM_MAP/_UNMAP to spec Albert Esteve
2025-08-14  8:37 ` [PATCH v6 4/8] vhost_user: Add frontend get_shmem_config command Albert Esteve
2025-08-14  8:37 ` [PATCH v6 5/8] vhost_user.rst: Add GET_SHMEM_CONFIG message Albert Esteve
2025-08-14  8:37 ` [PATCH v6 6/8] tests/qtest: Add GET_SHMEM validation test Albert Esteve
2025-08-14  8:37 ` [PATCH v6 7/8] qmp: add shmem feature map Albert Esteve
2025-08-14  8:37 ` [PATCH v6 8/8] vhost-user-device: Add shared memory BAR Albert Esteve

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=20250814083749.1317197-3-aesteve@redhat.com \
    --to=aesteve@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=david@redhat.com \
    --cc=dbassey@redhat.com \
    --cc=farosas@suse.de \
    --cc=hi@alyssa.is \
    --cc=jasowang@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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).