search for: vhost_vdpa_reset_device

...ion of its own rather than what the vhost-vdpa iotlb abstraction wishes to expose to userspace in the first place. If you ever look into QEMU's vhost_vdpa_reset_status() function, you may see memory_listener_unregister() will be called to evict all of the existing iotlb mappings right after vhost_vdpa_reset_device() across device reset, and later on at vhost_vdpa_dev_start(), memory_listener_register() will set up all iotlb mappings again. In an ideal world without this on-chip iommu deficiency QEMU should not have to behave this way - this is what I mentioned earlier that userspace had already noticed...

...straction wishes to expose to userspace in the first place. That's my understanding as well. > > If you ever look into QEMU's vhost_vdpa_reset_status() function, you may > see memory_listener_unregister() will be called to evict all of the > existing iotlb mappings right after vhost_vdpa_reset_device() across > device reset, and later on at vhost_vdpa_dev_start(), > memory_listener_register() will set up all iotlb mappings again. In an > ideal world without this on-chip iommu deficiency QEMU should not have > to behave this way - this is what I mentioned earlier that userspace had &...

On Wed, Aug 16, 2023 at 6:31?AM Si-Wei Liu <si-wei.liu at oracle.com> wrote: > > > > On 8/14/2023 7:25 PM, Jason Wang wrote: > > On Tue, Aug 15, 2023 at 9:45?AM Si-Wei Liu <si-wei.liu at oracle.com> wrote: > >> Signed-off-by: Si-Wei Liu <si-wei.liu at oracle.com> > >> --- > >> drivers/vhost/vdpa.c | 16 +++++++++++++++-