search for: vhost_iotlb_access_fail

...t_iotlb_msg { ??? __u64 iova; ??? __u64 size; ??? __u64 uaddr; #define VHOST_ACCESS_RO????? 0x1 #define VHOST_ACCESS_WO????? 0x2 #define VHOST_ACCESS_RW????? 0x3 ??? __u8 perm; #define VHOST_IOTLB_MISS?????????? 1 #define VHOST_IOTLB_UPDATE???????? 2 #define VHOST_IOTLB_INVALIDATE???? 3 #define VHOST_IOTLB_ACCESS_FAIL??? 4 ??? __u8 type; }; #define VHOST_IOTLB_MSG 0x1 #define VHOST_IOTLB_MSG_V2 0x2 struct vhost_msg { ??? int type; ??? union { ??? ??? struct vhost_iotlb_msg iotlb; ??? ??? __u8 padding[64]; ??? }; }; struct vhost_msg_v2 { ??? __u32 type; ??? __u32 reserved; ??? union { ??? ??? struct...

...t_iotlb_msg { ??? __u64 iova; ??? __u64 size; ??? __u64 uaddr; #define VHOST_ACCESS_RO????? 0x1 #define VHOST_ACCESS_WO????? 0x2 #define VHOST_ACCESS_RW????? 0x3 ??? __u8 perm; #define VHOST_IOTLB_MISS?????????? 1 #define VHOST_IOTLB_UPDATE???????? 2 #define VHOST_IOTLB_INVALIDATE???? 3 #define VHOST_IOTLB_ACCESS_FAIL??? 4 ??? __u8 type; }; #define VHOST_IOTLB_MSG 0x1 #define VHOST_IOTLB_MSG_V2 0x2 struct vhost_msg { ??? int type; ??? union { ??? ??? struct vhost_iotlb_msg iotlb; ??? ??? __u8 padding[64]; ??? }; }; struct vhost_msg_v2 { ??? __u32 type; ??? __u32 reserved; ??? union { ??? ??? struct...

...t; #define VHOST_ACCESS_RO????? 0x1 >> #define VHOST_ACCESS_WO????? 0x2 >> #define VHOST_ACCESS_RW????? 0x3 >> ??? __u8 perm; >> #define VHOST_IOTLB_MISS?????????? 1 >> #define VHOST_IOTLB_UPDATE???????? 2 >> #define VHOST_IOTLB_INVALIDATE???? 3 >> #define VHOST_IOTLB_ACCESS_FAIL??? 4 >> ??? __u8 type; >> }; >> >> #define VHOST_IOTLB_MSG 0x1 >> #define VHOST_IOTLB_MSG_V2 0x2 >> >> struct vhost_msg { >> ??? int type; >> ??? union { >> ??? ??? struct vhost_iotlb_msg iotlb; >> ??? ??? __u8 padding[64]; >...

...t; #define VHOST_ACCESS_RO????? 0x1 >> #define VHOST_ACCESS_WO????? 0x2 >> #define VHOST_ACCESS_RW????? 0x3 >> ??? __u8 perm; >> #define VHOST_IOTLB_MISS?????????? 1 >> #define VHOST_IOTLB_UPDATE???????? 2 >> #define VHOST_IOTLB_INVALIDATE???? 3 >> #define VHOST_IOTLB_ACCESS_FAIL??? 4 >> ??? __u8 type; >> }; >> >> #define VHOST_IOTLB_MSG 0x1 >> #define VHOST_IOTLB_MSG_V2 0x2 >> >> struct vhost_msg { >> ??? int type; >> ??? union { >> ??? ??? struct vhost_iotlb_msg iotlb; >> ??? ??? __u8 padding[64]; >...

...nux/vhost_types.h > index 669457ce5c48..5c12faffdde9 100644 > --- a/include/uapi/linux/vhost_types.h > +++ b/include/uapi/linux/vhost_types.h > @@ -60,6 +60,13 @@ struct vhost_iotlb_msg { > #define VHOST_IOTLB_UPDATE 2 > #define VHOST_IOTLB_INVALIDATE 3 > #define VHOST_IOTLB_ACCESS_FAIL 4 > +/* VHOST_IOTLB_BATCH_BEGIN is a hint that userspace will update > + * several mappings afterwards. VHOST_IOTLB_BATCH_END is a hint that > + * userspace had finished the mapping updating. Well not just hints - in fact updates do not take place until _END. How about: /* VHOST_IOT...

...nux/vhost_types.h > index 669457ce5c48..5c12faffdde9 100644 > --- a/include/uapi/linux/vhost_types.h > +++ b/include/uapi/linux/vhost_types.h > @@ -60,6 +60,13 @@ struct vhost_iotlb_msg { > #define VHOST_IOTLB_UPDATE 2 > #define VHOST_IOTLB_INVALIDATE 3 > #define VHOST_IOTLB_ACCESS_FAIL 4 > +/* VHOST_IOTLB_BATCH_BEGIN is a hint that userspace will update > + * several mappings afterwards. VHOST_IOTLB_BATCH_END is a hint that > + * userspace had finished the mapping updating. Well not just hints - in fact updates do not take place until _END. How about: /* VHOST_IOT...

...ine VHOST_ACCESS_WO????? 0x2 >>>> #define VHOST_ACCESS_RW????? 0x3 >>>> ??? __u8 perm; >>>> #define VHOST_IOTLB_MISS?????????? 1 >>>> #define VHOST_IOTLB_UPDATE???????? 2 >>>> #define VHOST_IOTLB_INVALIDATE???? 3 >>>> #define VHOST_IOTLB_ACCESS_FAIL??? 4 >>>> ??? __u8 type; >>>> }; >>>> >>>> #define VHOST_IOTLB_MSG 0x1 >>>> #define VHOST_IOTLB_MSG_V2 0x2 >>>> >>>> struct vhost_msg { >>>> ??? int type; >>>> ??? union { >>>&...

...ize; > ??? __u64 uaddr; > #define VHOST_ACCESS_RO????? 0x1 > #define VHOST_ACCESS_WO????? 0x2 > #define VHOST_ACCESS_RW????? 0x3 > ??? __u8 perm; > #define VHOST_IOTLB_MISS?????????? 1 > #define VHOST_IOTLB_UPDATE???????? 2 > #define VHOST_IOTLB_INVALIDATE???? 3 > #define VHOST_IOTLB_ACCESS_FAIL??? 4 > ??? __u8 type; > }; > > #define VHOST_IOTLB_MSG 0x1 > #define VHOST_IOTLB_MSG_V2 0x2 > > struct vhost_msg { > ??? int type; > ??? union { > ??? ??? struct vhost_iotlb_msg iotlb; > ??? ??? __u8 padding[64]; > ??? }; > }; > > struct vhost_msg_v2...

...> > > --- a/include/uapi/linux/vhost_types.h > > > +++ b/include/uapi/linux/vhost_types.h > > > @@ -60,6 +60,13 @@ struct vhost_iotlb_msg { > > > #define VHOST_IOTLB_UPDATE 2 > > > #define VHOST_IOTLB_INVALIDATE 3 > > > #define VHOST_IOTLB_ACCESS_FAIL 4 > > > +/* VHOST_IOTLB_BATCH_BEGIN is a hint that userspace will update > > > + * several mappings afterwards. VHOST_IOTLB_BATCH_END is a hint that > > > + * userspace had finished the mapping updating. > > > > Well not just hints - in fact updates do not...

On 2020/2/5 ??10:05, Tiwei Bie wrote: > On Tue, Feb 04, 2020 at 02:46:16PM +0800, Jason Wang wrote: >> On 2020/2/4 ??2:01, Michael S. Tsirkin wrote: >>> On Tue, Feb 04, 2020 at 11:30:11AM +0800, Jason Wang wrote: >>>> 5) generate diffs of memory table and using IOMMU API to setup the dma >>>> mapping in this method >>> Frankly I think that's a

On 2020/2/5 ??10:05, Tiwei Bie wrote: > On Tue, Feb 04, 2020 at 02:46:16PM +0800, Jason Wang wrote: >> On 2020/2/4 ??2:01, Michael S. Tsirkin wrote: >>> On Tue, Feb 04, 2020 at 11:30:11AM +0800, Jason Wang wrote: >>>> 5) generate diffs of memory table and using IOMMU API to setup the dma >>>> mapping in this method >>> Frankly I think that's a

...gt; > #define VHOST_ACCESS_WO????? 0x2 > > > #define VHOST_ACCESS_RW????? 0x3 > > > ??? __u8 perm; > > > #define VHOST_IOTLB_MISS?????????? 1 > > > #define VHOST_IOTLB_UPDATE???????? 2 > > > #define VHOST_IOTLB_INVALIDATE???? 3 > > > #define VHOST_IOTLB_ACCESS_FAIL??? 4 > > > ??? __u8 type; > > > }; > > > > > > #define VHOST_IOTLB_MSG 0x1 > > > #define VHOST_IOTLB_MSG_V2 0x2 > > > > > > struct vhost_msg { > > > ??? int type; > > > ??? union { > > > ??? ??? struct v...

...nux/vhost_types.h b/include/uapi/linux/vhost_types.h index 669457ce5c48..5c12faffdde9 100644 --- a/include/uapi/linux/vhost_types.h +++ b/include/uapi/linux/vhost_types.h @@ -60,6 +60,13 @@ struct vhost_iotlb_msg { #define VHOST_IOTLB_UPDATE 2 #define VHOST_IOTLB_INVALIDATE 3 #define VHOST_IOTLB_ACCESS_FAIL 4 +/* VHOST_IOTLB_BATCH_BEGIN is a hint that userspace will update + * several mappings afterwards. VHOST_IOTLB_BATCH_END is a hint that + * userspace had finished the mapping updating. When those two flags + * were set, kernel will ignore the rest fileds of the IOTLB message. + */ +#define VHOS...

...x 669457ce5c48..5c12faffdde9 100644 >> --- a/include/uapi/linux/vhost_types.h >> +++ b/include/uapi/linux/vhost_types.h >> @@ -60,6 +60,13 @@ struct vhost_iotlb_msg { >> #define VHOST_IOTLB_UPDATE 2 >> #define VHOST_IOTLB_INVALIDATE 3 >> #define VHOST_IOTLB_ACCESS_FAIL 4 >> +/* VHOST_IOTLB_BATCH_BEGIN is a hint that userspace will update >> + * several mappings afterwards. VHOST_IOTLB_BATCH_END is a hint that >> + * userspace had finished the mapping updating. > > Well not just hints - in fact updates do not take place > until _END....

Hi all: This series tries to support batched IOTLB updating vhost-vdpa. Currently vhost-vdpa accepts userspace mapping via IOTLB API, and it can only forward one mapping to IOMMU or device through IOMMU API or dma_map(). Though set_map() is deisgend to have the capability to pass an rbtree based mapping to vDPA device, it's still be called at least once for each VHOST_IOTLB_UPDATE or

Hi all: This series tries to support batched IOTLB updating vhost-vdpa. Currently vhost-vdpa accepts userspace mapping via IOTLB API, and it can only forward one mapping to IOMMU or device through IOMMU API or dma_map(). Though set_map() is designed to have the capability to pass an rbtree based mapping to vDPA device, it's still be called at least once for each VHOST_IOTLB_UPDATE or

...t.h, the vhost msg structure has everything needed for map/unmap operations: struct vhost_iotlb_msg { __u64 iova; __u64 size; __u64 uaddr; __u8 perm; /* R/W */ __u8 type; #define VHOST_IOTLB_MISS #define VHOST_IOTLB_UPDATE /* MAP */ #define VHOST_IOTLB_INVALIDATE /* UNMAP */ #define VHOST_IOTLB_ACCESS_FAIL }; struct vhost_msg { int type; union { struct vhost_iotlb_msg iotlb; __u8 padding[64]; }; }; The vhost-iommu device associates a virtual device ID to a TLB fd. We should be able to use the same commands for [vhost-net <-> virtio-iommu] and [virtio-net <-> vhost-iommu]...

...vhost_iotlb_msg { + __u64 iova; + __u64 size; + __u64 uaddr; +#define VHOST_ACCESS_RO 0x1 +#define VHOST_ACCESS_WO 0x2 +#define VHOST_ACCESS_RW 0x3 + __u8 perm; +#define VHOST_IOTLB_MISS 1 +#define VHOST_IOTLB_UPDATE 2 +#define VHOST_IOTLB_INVALIDATE 3 +#define VHOST_IOTLB_ACCESS_FAIL 4 + __u8 type; +}; + +#define VHOST_IOTLB_MSG 0x1 + +struct vhost_msg { + int type; + union { + struct vhost_iotlb_msg iotlb; + __u8 padding[64]; + }; +}; + struct vhost_memory_region { __u64 guest_phys_addr; __u64 memory_size; /* bytes */ @@ -146,6 +172,8 @@ struct vhost_memory { #defin...

This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace IOMMU implementation (qemu) for a secure DMA environment (DMAR) in guest. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the translation, this is done through: - when there's a IOTLB miss, it will notify userspace through

This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace IOMMU implementation (qemu) for a secure DMA environment (DMAR) in guest. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the translation, this is done through: - when there's a IOTLB miss, it will notify userspace through