Searched hist:f1f9e6c5961ffb36fd4a81cd7edcded7bfad2ab2 (Results 1 – 2 of 2) sorted by relevance
/qemu/include/hw/virtio/ |
H A D | vhost.h | f1f9e6c5961ffb36fd4a81cd7edcded7bfad2ab2 Fri Nov 04 08:39:15 UTC 2016 Greg Kurz <groug@kaod.org> vhost: adapt vhost_verify_ring_mappings() to virtio 1 ring layout
With virtio 1, the vring layout is split in 3 separate regions of contiguous memory for the descriptor table, the available ring and the used ring, as opposed with legacy virtio which uses a single region.
In case of memory re-mapping, the code ensures it doesn't affect the vring mapping. This is done in vhost_verify_ring_mappings() which assumes the device is legacy.
This patch changes vhost_verify_ring_mappings() to check the mappings of each part of the vring separately.
This works for legacy mappings as well.
Cc: qemu-stable@nongnu.org Signed-off-by: Greg Kurz <groug@kaod.org> Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
|
/qemu/hw/virtio/ |
H A D | vhost.c | f1f9e6c5961ffb36fd4a81cd7edcded7bfad2ab2 Fri Nov 04 08:39:15 UTC 2016 Greg Kurz <groug@kaod.org> vhost: adapt vhost_verify_ring_mappings() to virtio 1 ring layout
With virtio 1, the vring layout is split in 3 separate regions of contiguous memory for the descriptor table, the available ring and the used ring, as opposed with legacy virtio which uses a single region.
In case of memory re-mapping, the code ensures it doesn't affect the vring mapping. This is done in vhost_verify_ring_mappings() which assumes the device is legacy.
This patch changes vhost_verify_ring_mappings() to check the mappings of each part of the vring separately.
This works for legacy mappings as well.
Cc: qemu-stable@nongnu.org Signed-off-by: Greg Kurz <groug@kaod.org> Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
|