Displaying 3 results from an estimated 3 matches for "vhost_vdpa_reset_status".
2023 Aug 16
1
[PATCH RFC 4/4] vhost-vdpa: introduce IOTLB_PERSIST backend feature bit
...y
backward to retain/emulate the flawed vhost-iotlb reset behavior for
older userspace - I consider it more of a bug in .set_map driver
implementation 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...
2023 Aug 22
1
[PATCH RFC 4/4] vhost-vdpa: introduce IOTLB_PERSIST backend feature bit
...ehavior for
> older userspace - I consider it more of a bug in .set_map driver
> implementation of its own rather than what the vhost-vdpa iotlb
> abstraction 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...
2023 Aug 16
1
[PATCH RFC 4/4] vhost-vdpa: introduce IOTLB_PERSIST backend feature bit
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 +++++++++++++++-