search for: _vring_

...>>> >>> 2) then it can allocate memory for ctrl vq and set its address through >>> vhost-mdev >>> >>> 3) userspace can populate ctrl vq itself >> I see. That is to say, userspace e.g. QEMU will program the >> ctrl vq with the existing VHOST_*_VRING_* ioctls, and parent >> drivers should know that the addresses used in ctrl vq are >> host virtual addresses in vhost-mdev's case. > > > That's really good point. And that means parent needs to differ vhost > from virtio. It should work. HVA may only work when we...

...>>> >>> 2) then it can allocate memory for ctrl vq and set its address through >>> vhost-mdev >>> >>> 3) userspace can populate ctrl vq itself >> I see. That is to say, userspace e.g. QEMU will program the >> ctrl vq with the existing VHOST_*_VRING_* ioctls, and parent >> drivers should know that the addresses used in ctrl vq are >> host virtual addresses in vhost-mdev's case. > > > That's really good point. And that means parent needs to differ vhost > from virtio. It should work. HVA may only work when we...

...like: > > 1) userspace find ctrl_vq is supported > > 2) then it can allocate memory for ctrl vq and set its address through > vhost-mdev > > 3) userspace can populate ctrl vq itself I see. That is to say, userspace e.g. QEMU will program the ctrl vq with the existing VHOST_*_VRING_* ioctls, and parent drivers should know that the addresses used in ctrl vq are host virtual addresses in vhost-mdev's case. > > > > > > > > > > > > > I think it might be better to do > > > > > > this in one generic vhost-mdev module....

...like: > > 1) userspace find ctrl_vq is supported > > 2) then it can allocate memory for ctrl vq and set its address through > vhost-mdev > > 3) userspace can populate ctrl vq itself I see. That is to say, userspace e.g. QEMU will program the ctrl vq with the existing VHOST_*_VRING_* ioctls, and parent drivers should know that the addresses used in ctrl vq are host virtual addresses in vhost-mdev's case. > > > > > > > > > > > > > I think it might be better to do > > > > > > this in one generic vhost-mdev module....

...it can allocate memory for ctrl vq and set its address through > > > > vhost-mdev > > > > > > > > 3) userspace can populate ctrl vq itself > > > I see. That is to say, userspace e.g. QEMU will program the > > > ctrl vq with the existing VHOST_*_VRING_* ioctls, and parent > > > drivers should know that the addresses used in ctrl vq are > > > host virtual addresses in vhost-mdev's case. > > > > > > That's really good point. And that means parent needs to differ vhost > > from virtio. It should wo...

...n allocate memory for ctrl vq and set its address through >>>>> vhost-mdev >>>>> >>>>> 3) userspace can populate ctrl vq itself >>>> I see. That is to say, userspace e.g. QEMU will program the >>>> ctrl vq with the existing VHOST_*_VRING_* ioctls, and parent >>>> drivers should know that the addresses used in ctrl vq are >>>> host virtual addresses in vhost-mdev's case. >>> >>> That's really good point. And that means parent needs to differ vhost >>> from virtio. It should w...

...n allocate memory for ctrl vq and set its address through >>>>> vhost-mdev >>>>> >>>>> 3) userspace can populate ctrl vq itself >>>> I see. That is to say, userspace e.g. QEMU will program the >>>> ctrl vq with the existing VHOST_*_VRING_* ioctls, and parent >>>> drivers should know that the addresses used in ctrl vq are >>>> host virtual addresses in vhost-mdev's case. >>> >>> That's really good point. And that means parent needs to differ vhost >>> from virtio. It should w...

...ce find ctrl_vq is supported >> >> 2) then it can allocate memory for ctrl vq and set its address through >> vhost-mdev >> >> 3) userspace can populate ctrl vq itself > I see. That is to say, userspace e.g. QEMU will program the > ctrl vq with the existing VHOST_*_VRING_* ioctls, and parent > drivers should know that the addresses used in ctrl vq are > host virtual addresses in vhost-mdev's case. That's really good point. And that means parent needs to differ vhost from virtio. It should work. But is there any chance to use DMA address? I'm as...

On Wed, Oct 23, 2019 at 03:25:00PM +0800, Jason Wang wrote: > On 2019/10/23 ??3:07, Tiwei Bie wrote: > > On Wed, Oct 23, 2019 at 01:46:23PM +0800, Jason Wang wrote: > > > On 2019/10/23 ??11:02, Tiwei Bie wrote: > > > > On Tue, Oct 22, 2019 at 09:30:16PM +0800, Jason Wang wrote: > > > > > On 2019/10/22 ??5:52, Tiwei Bie wrote: > > > > >

On Wed, Oct 23, 2019 at 03:25:00PM +0800, Jason Wang wrote: > On 2019/10/23 ??3:07, Tiwei Bie wrote: > > On Wed, Oct 23, 2019 at 01:46:23PM +0800, Jason Wang wrote: > > > On 2019/10/23 ??11:02, Tiwei Bie wrote: > > > > On Tue, Oct 22, 2019 at 09:30:16PM +0800, Jason Wang wrote: > > > > > On 2019/10/22 ??5:52, Tiwei Bie wrote: > > > > >