* [PATCH v1] docs/vhost-user: clarify the semantics of VHOST_USER_SET_VRING_ENABLE
@ 2026-03-25 11:36 Daniil Tatianin
0 siblings, 0 replies; only message in thread
From: Daniil Tatianin @ 2026-03-25 11:36 UTC (permalink / raw)
To: Michael S. Tsirkin
Cc: Daniil Tatianin, Stefano Garzarella, Pierrick Bouvier, qemu-devel,
yc-core, Vladimir Sementsov-Ogievskiy
Documentation didn't really make it clear that the payload contains any
sort of desired state field, you could only derive that by looking at
the QEMU implementation of this request. Add an extra note to make that
clear.
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Signed-off-by: Daniil Tatianin <d-tatianin@yandex-team.ru>
---
Changes since v0:
- Remove 'Note that' (suggested by Vladimir)
---
docs/interop/vhost-user.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/interop/vhost-user.rst b/docs/interop/vhost-user.rst
index 137c9f3669d..e29eb291f11 100644
--- a/docs/interop/vhost-user.rst
+++ b/docs/interop/vhost-user.rst
@@ -1346,6 +1346,8 @@ Front-end message types
:reply payload: N/A
Signal the back-end to enable or disable corresponding vring.
+ The ``num`` field contains the target vring state where 0 means disabled,
+ and any other value means enabled.
This request should be sent only when
``VHOST_USER_F_PROTOCOL_FEATURES`` has been negotiated.
--
2.34.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2026-03-25 11:37 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-25 11:36 [PATCH v1] docs/vhost-user: clarify the semantics of VHOST_USER_SET_VRING_ENABLE Daniil Tatianin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox