[Qemu-devel] [PATCH v3 2/3] spec/vhost-user: add VHOST_USER_PROTOCOL_F_SET_DEVICE_ID

[Wei Wang <wei.w.wang@intel.com>]

The VHOST_USER_PROTOCOL_F_SET_DEVICE_ID protocol feature indicates
that the slave side implementation supports different types of devices.
The master tells the slave what type of device to create by sending
a VHOST_USER_SET_DEVICE_ID message.

Signed-off-by: Wei Wang <wei.w.wang@intel.com>
---
 docs/specs/vhost-user.txt | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/specs/vhost-user.txt b/docs/specs/vhost-user.txt
index 18e49d0..80dcfc1 100644
--- a/docs/specs/vhost-user.txt
+++ b/docs/specs/vhost-user.txt
@@ -267,6 +267,7 @@ Protocol features
 #define VHOST_USER_PROTOCOL_F_RARP           2
 #define VHOST_USER_PROTOCOL_F_REPLY_ACK      3
 #define VHOST_USER_PROTOCOL_F_VHOST_PCI      4
+#define VHOST_USER_PROTOCOL_F_SET_DEVICE_ID  5
 
 Message types
 -------------
@@ -479,6 +480,16 @@ Message types
       The first 6 bytes of the payload contain the mac address of the guest to
       allow the vhost user backend to construct and broadcast the fake RARP.
 
+ * VHOST_USER_SET_DEVICE_ID
+      Id: 20
+      Equivalent ioctl: N/A
+      Master payload: u64
+
+      The master sends the virtio device id to the slave. The virtio device id
+      indicates the device type of the master device.
+      This request should be sent only when VHOST_USER_PROTOCOL_F_SET_DEVICE_ID
+      has been negotiated.
+
 VHOST_USER_PROTOCOL_F_REPLY_ACK:
 -------------------------------
 The original vhost-user specification only demands replies for certain
-- 
2.7.4