search for: vhostuserrequest

...onfig to userspace. The set_config and get_config interface isn't really everything of device specific settings. We also have ctrlq in virtio-net. > > > > I think it might be better to do > > this in one generic vhost-mdev module. > > > Looking at definitions of VhostUserRequest in qemu, it mixed generic API > with device specific API. If we want go this ways (a generic vhost-mdev), > more questions needs to be answered: > > 1) How could userspace know which type of vhost it would use? Do we need to > expose virtio subsystem device in for userspace this cas...

...onfig to userspace. The set_config and get_config interface isn't really everything of device specific settings. We also have ctrlq in virtio-net. > > > > I think it might be better to do > > this in one generic vhost-mdev module. > > > Looking at definitions of VhostUserRequest in qemu, it mixed generic API > with device specific API. If we want go this ways (a generic vhost-mdev), > more questions needs to be answered: > > 1) How could userspace know which type of vhost it would use? Do we need to > expose virtio subsystem device in for userspace this cas...

...d let parent to deal with that. I mean how to expose ctrlq related settings to userspace? > > > > > > > > > > > I think it might be better to do > > > > this in one generic vhost-mdev module. > > > > > > Looking at definitions of VhostUserRequest in qemu, it mixed generic API > > > with device specific API. If we want go this ways (a generic vhost-mdev), > > > more questions needs to be answered: > > > > > > 1) How could userspace know which type of vhost it would use? Do we need to > > > expose...

...d let parent to deal with that. I mean how to expose ctrlq related settings to userspace? > > > > > > > > > > > I think it might be better to do > > > > this in one generic vhost-mdev module. > > > > > > Looking at definitions of VhostUserRequest in qemu, it mixed generic API > > > with device specific API. If we want go this ways (a generic vhost-mdev), > > > more questions needs to be answered: > > > > > > 1) How could userspace know which type of vhost it would use? Do we need to > > > expose...

...q in virtio-net. Yes, but it could be processed by the exist API. Isn't it? Just set ctrl vq address and let parent to deal with that. > >> >>> I think it might be better to do >>> this in one generic vhost-mdev module. >> >> Looking at definitions of VhostUserRequest in qemu, it mixed generic API >> with device specific API. If we want go this ways (a generic vhost-mdev), >> more questions needs to be answered: >> >> 1) How could userspace know which type of vhost it would use? Do we need to >> expose virtio subsystem device in for...

...dresses 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. > > > > > Looking at definitions of VhostUserRequest in qemu, it mixed generic API > > > > > with device specific API. If we want go this ways (a generic vhost-mdev), > > > > > more questions needs to be answered: > > > > > > > > > > 1) How could userspace know which type of vhost it would...

...dresses 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. > > > > > Looking at definitions of VhostUserRequest in qemu, it mixed generic API > > > > > with device specific API. If we want go this ways (a generic vhost-mdev), > > > > > more questions needs to be answered: > > > > > > > > > > 1) How could userspace know which type of vhost it would...

...2) then it can allocate memory for ctrl vq and set its address through vhost-mdev 3) userspace can populate ctrl vq itself > >> >>>>> I think it might be better to do >>>>> this in one generic vhost-mdev module. >>>> Looking at definitions of VhostUserRequest in qemu, it mixed generic API >>>> with device specific API. If we want go this ways (a generic vhost-mdev), >>>> more questions needs to be answered: >>>> >>>> 1) How could userspace know which type of vhost it would use? Do we need to >>>&g...

...s there any chance to use DMA address? I'm asking since the API then tends to be device specific. > >> >>>>>>> I think it might be better to do >>>>>>> this in one generic vhost-mdev module. >>>>>> Looking at definitions of VhostUserRequest in qemu, it mixed generic API >>>>>> with device specific API. If we want go this ways (a generic vhost-mdev), >>>>>> more questions needs to be answered: >>>>>> >>>>>> 1) How could userspace know which type of vhost it would u...

On Tue, Oct 22, 2019 at 09:30:16PM +0800, Jason Wang wrote: > On 2019/10/22 ??5:52, Tiwei Bie wrote: > > This patch introduces a mdev based hardware vhost backend. > > This backend is built on top of the same abstraction used > > in virtio-mdev and provides a generic vhost interface for > > userspace to accelerate the virtio devices in guest. > > > > This

On Tue, Oct 22, 2019 at 09:30:16PM +0800, Jason Wang wrote: > On 2019/10/22 ??5:52, Tiwei Bie wrote: > > This patch introduces a mdev based hardware vhost backend. > > This backend is built on top of the same abstraction used > > in virtio-mdev and provides a generic vhost interface for > > userspace to accelerate the virtio devices in guest. > > > > This

...figs between parent and userspace and even won't > cache any info when possible, So it looks to me this is only possible if we expose e.g set_config and get_config to userspace. > I think it might be better to do > this in one generic vhost-mdev module. Looking at definitions of VhostUserRequest in qemu, it mixed generic API with device specific API. If we want go this ways (a generic vhost-mdev), more questions needs to be answered: 1) How could userspace know which type of vhost it would use? Do we need to expose virtio subsystem device in for userspace this case? 2) That generic vh...