diff options
| author | Raphael Norwitz | 2020-05-21 07:00:59 +0200 |
|---|---|---|
| committer | Michael S. Tsirkin | 2020-06-12 16:17:06 +0200 |
| commit | b650d5f4b1cd3f9f8c4fdb319838c5c1e0695e41 (patch) | |
| tree | 1cbd55733022ae58e25859c57e0a38e309d904af /include | |
| parent | Support individual region unmap in libvhost-user (diff) | |
| download | qemu-b650d5f4b1cd3f9f8c4fdb319838c5c1e0695e41.tar.gz qemu-b650d5f4b1cd3f9f8c4fdb319838c5c1e0695e41.tar.xz qemu-b650d5f4b1cd3f9f8c4fdb319838c5c1e0695e41.zip | |
Lift max ram slots limit in libvhost-user
Historically, VMs with vhost-user devices could hot-add memory a maximum
of 8 times. Now that the VHOST_USER_PROTOCOL_F_CONFIGURE_MEM_SLOTS
protocol feature has been added, VMs with vhost-user backends which
support this new feature can support a configurable number of ram slots
up to the maximum supported by the target platform.
This change adds VHOST_USER_PROTOCOL_F_CONFIGURE_MEM_SLOTS support for
backends built with libvhost-user, and increases the number of supported
ram slots from 8 to 32.
Memory hot-add, hot-remove and postcopy migration were tested with
the vhost-user-bridge sample.
Signed-off-by: Raphael Norwitz <raphael.norwitz@nutanix.com>
Message-Id: <1588533678-23450-11-git-send-email-raphael.norwitz@nutanix.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions