3 Commits

Author	SHA1	Message	Date
Sebastien Boeuf	620aaf234e	vfio_user: DmaUnmap expects a reply with payload ... The current code was expecting a reply with only the header, which wasn't reading the rest of payload that was provided. This was causing the following replies to be completely wrong as they were shifted by the previous payload that wasn't read. The simple way to fix this issue is by reading the header and the expected payload when getting a reply from a DmaUnmap request. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>	2021-08-17 09:03:43 -07:00
Rob Bradford	d13eea3ba1	vfio_user: Fix debug output to include reply for DeviceGetRegionInfo ... The reply was being printed before it had been read so it was just showing the default values. Signed-off-by: Rob Bradford <robert.bradford@intel.com>	2021-08-12 13:19:04 +01:00
Rob Bradford	2e236c53c8	vfio_user: Implement client side support ... Implement (most) of the client side (i.e. VMM side) of the vfio-user protocol: https://github.com/nutanix/libvfio-user/blob/master/docs/vfio-user.rst Items that are not implemented (because they are optimisations or unused due to alternative solutions: * VFIO_USER_DMA_READ/WRITE - this is a way for the server to read guest memory if the guest memory is not shared by fd where the client doesn't support it. However since we do support sharing the memory by fd this is not required. * VFIO_USER_GET_REGION_IO_FDS - an optimisation to bypass the VMM by having KVM talk directly to the backend using ioregionfd * VFIO_USER_DIRTY_PAGES - for the implementation of live migration Signed-off-by: Rob Bradford <robert.bradford@intel.com>	2021-08-10 16:01:00 +01:00