Add VHOST_USER_PROTOCOL_F_CONFIGURE_MEM_SLOTS
authorRaphael Norwitz <raphael.norwitz@nutanix.com>
Thu, 21 May 2020 05:00:32 +0000 (05:00 +0000)
committerMichael S. Tsirkin <mst@redhat.com>
Fri, 12 Jun 2020 14:17:06 +0000 (10:17 -0400)
commit6b0eff1a4ea47c835a7d8bee88c05c47ada37495
tree17ed939bd48af59b703e44c71d894ec30b6f55a5
parent23374a84c5f08e20ec2506a6322330d51f9134c5
Add VHOST_USER_PROTOCOL_F_CONFIGURE_MEM_SLOTS

This change introduces a new feature to the vhost-user protocol allowing
a backend device to specify the maximum number of ram slots it supports.

At this point, the value returned by the backend will be capped at the
maximum number of ram slots which can be supported by vhost-user, which
is currently set to 8 because of underlying protocol limitations.

The returned value will be stored inside the VhostUserState struct so
that on device reconnect we can verify that the ram slot limitation
has not decreased since the last time the device connected.

Signed-off-by: Raphael Norwitz <raphael.norwitz@nutanix.com>
Signed-off-by: Peter Turschmid <peter.turschm@nutanix.com>
Message-Id: <1588533678-23450-4-git-send-email-raphael.norwitz@nutanix.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
docs/interop/vhost-user.rst
hw/virtio/vhost-user.c
include/hw/virtio/vhost-user.h