search for: vhost_update_iotlb

...l the translation request in a preset userspace address (This address is set through ioctl VHOST_SET_IOTLB_REQUEST_ENTRY). - Notify userspace through eventfd (This eventfd was set through ioctl VHOST_SET_IOTLB_FD). When userspace finishes the translation, it will update the vhost IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of snooping the IOTLB invalidation of IOMMU IOTLB and use VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. For simplicity, IOTLB was implemented with a simple hash array. The index were calculated from IOVA page frame number which can only works at P...

...l the translation request in a preset userspace address (This address is set through ioctl VHOST_SET_IOTLB_REQUEST_ENTRY). - Notify userspace through eventfd (This eventfd was set through ioctl VHOST_SET_IOTLB_FD). When userspace finishes the translation, it will update the vhost IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of snooping the IOTLB invalidation of IOMMU IOTLB and use VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. For simplicity, IOTLB was implemented with a simple hash array. The index were calculated from IOVA page frame number which can only works at P...

...preset userspace address (This > address is set through ioctl VHOST_SET_IOTLB_REQUEST_ENTRY). > - Notify userspace through eventfd (This eventfd was set through ioctl > VHOST_SET_IOTLB_FD). > > When userspace finishes the translation, it will update the vhost > IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of > snooping the IOTLB invalidation of IOMMU IOTLB and use > VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. Is there any performance data shows the difference with IOTLB supporting? I doubt we may see performance decrease since the flush co...

...on-blocking flag. It's not useful for other ioctls but it's useful here. > > > >> - device IOTLB were started and stopped through VHOST_RUN_IOTLB ioctl > >> > >> When userspace finishes the translation, it will update the vhost > >> IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of > >> snooping the IOTLB invalidation of IOMMU IOTLB and use > >> VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. > > There's one problem here, and that is that VQs still do not undergo > > translation. In theory...

...on-blocking flag. It's not useful for other ioctls but it's useful here. > > > >> - device IOTLB were started and stopped through VHOST_RUN_IOTLB ioctl > >> > >> When userspace finishes the translation, it will update the vhost > >> IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of > >> snooping the IOTLB invalidation of IOMMU IOTLB and use > >> VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. > > There's one problem here, and that is that VQs still do not undergo > > translation. In theory...

...dress is set through ioctl VHOST_SET_IOTLB_REQUEST_ENTRY). >>> - Notify userspace through eventfd (This eventfd was set through ioctl >>> VHOST_SET_IOTLB_FD). >>> >>> When userspace finishes the translation, it will update the vhost >>> IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of >>> snooping the IOTLB invalidation of IOMMU IOTLB and use >>> VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. >> >> Is there any performance data shows the difference with IOTLB supporting? > > Basic testing sh...

...dress is set through ioctl VHOST_SET_IOTLB_REQUEST_ENTRY). >>> - Notify userspace through eventfd (This eventfd was set through ioctl >>> VHOST_SET_IOTLB_FD). >>> >>> When userspace finishes the translation, it will update the vhost >>> IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of >>> snooping the IOTLB invalidation of IOMMU IOTLB and use >>> VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. >> >> Is there any performance data shows the difference with IOTLB supporting? > > Basic testing sh...

...ens to be what kvm wants, but here - why don't we just add a generic support for reading out events on the vhost fd itself? > - device IOTLB were started and stopped through VHOST_RUN_IOTLB ioctl > > When userspace finishes the translation, it will update the vhost > IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of > snooping the IOTLB invalidation of IOMMU IOTLB and use > VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. There's one problem here, and that is that VQs still do not undergo translation. In theory VQ could be mapped in such a way that...

...ens to be what kvm wants, but here - why don't we just add a generic support for reading out events on the vhost fd itself? > - device IOTLB were started and stopped through VHOST_RUN_IOTLB ioctl > > When userspace finishes the translation, it will update the vhost > IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of > snooping the IOTLB invalidation of IOMMU IOTLB and use > VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. There's one problem here, and that is that VQs still do not undergo translation. In theory VQ could be mapped in such a way that...

...preset userspace address (This > address is set through ioctl VHOST_SET_IOTLB_REQUEST_ENTRY). > - Notify userspace through eventfd (This eventfd was set through ioctl > VHOST_SET_IOTLB_FD). > > When userspace finishes the translation, it will update the vhost > IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of > snooping the IOTLB invalidation of IOMMU IOTLB and use > VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. > > For simplicity, IOTLB was implemented with a simple hash array. The > index were calculated from IOVA page frame number...

...advantages of this? I mean looks like all other ioctls could be done through vhost fd reading/writing too. > >> - device IOTLB were started and stopped through VHOST_RUN_IOTLB ioctl >> >> When userspace finishes the translation, it will update the vhost >> IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of >> snooping the IOTLB invalidation of IOMMU IOTLB and use >> VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. > There's one problem here, and that is that VQs still do not undergo > translation. In theory VQ could be mapped i...

...t useful for other ioctls but it's useful here. > Ok, this looks better. >>>> - device IOTLB were started and stopped through VHOST_RUN_IOTLB ioctl >>>> >>>> When userspace finishes the translation, it will update the vhost >>>> IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of >>>> snooping the IOTLB invalidation of IOMMU IOTLB and use >>>> VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. >>> There's one problem here, and that is that VQs still do not undergo >>> translation....

...(This >> address is set through ioctl VHOST_SET_IOTLB_REQUEST_ENTRY). >> - Notify userspace through eventfd (This eventfd was set through ioctl >> VHOST_SET_IOTLB_FD). >> >> When userspace finishes the translation, it will update the vhost >> IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of >> snooping the IOTLB invalidation of IOMMU IOTLB and use >> VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. > > Is there any performance data shows the difference with IOTLB supporting? Basic testing show it was slower than wit...

...s is set through ioctl VHOST_SET_IOTLB_REQUEST_ENTRY). - Notify userspace through eventfd (This eventfd was set through ioctl VHOST_SET_IOTLB_FD). - device IOTLB were started and stopped through VHOST_RUN_IOTLB ioctl When userspace finishes the translation, it will update the vhost IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of snooping the IOTLB invalidation of IOMMU IOTLB and use VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. Signed-off-by: Jason Wang <jasowang at redhat.com> --- drivers/vhost/net.c | 6 +- drivers/vhost/vhost.c | 301 +++++++++++...

...l the translation request in a preset userspace address (This address is set through ioctl VHOST_SET_IOTLB_REQUEST_ENTRY). - Notify userspace through eventfd (This eventfd was set through ioctl VHOST_SET_IOTLB_FD). When userspace finishes the translation, it will update the vhost IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of snooping the IOTLB invalidation of IOMMU IOTLB and use VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. The codes were designed to be architecture independent. It should be easily ported to any architecture. Changes from V1: - support any size/ra...

...l the translation request in a preset userspace address (This address is set through ioctl VHOST_SET_IOTLB_REQUEST_ENTRY). - Notify userspace through eventfd (This eventfd was set through ioctl VHOST_SET_IOTLB_FD). When userspace finishes the translation, it will update the vhost IOTLB through VHOST_UPDATE_IOTLB ioctl. Userspace is also in charge of snooping the IOTLB invalidation of IOMMU IOTLB and use VHOST_UPDATE_IOTLB to invalidate the possible entry in vhost. The codes were designed to be architecture independent. It should be easily ported to any architecture. Changes from V1: - support any size/ra...