search for: set_vring_call

...nventing a new protocol? > > > > I'm trying to make it work in VFIO's way.. > > > > > > > > > I believe either of the following should be better: > > > > > > > > > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > > > > > extend it with e.g notify region. The advantages is that all exist userspace > > > > > program could be reused without modification (or minimal modification). And > > > > > vhost API hides lots of details that is not necessary to be underst...

...nventing a new protocol? > > > > I'm trying to make it work in VFIO's way.. > > > > > > > > > I believe either of the following should be better: > > > > > > > > > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > > > > > extend it with e.g notify region. The advantages is that all exist userspace > > > > > program could be reused without modification (or minimal modification). And > > > > > vhost API hides lots of details that is not necessary to be underst...

...a comments like V1. What's the advantage of inventing a new protocol? > > I'm trying to make it work in VFIO's way.. > > > > > I believe either of the following should be better: > > > > > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > > > extend it with e.g notify region. The advantages is that all exist userspace > > > program could be reused without modification (or minimal modification). And > > > vhost API hides lots of details that is not necessary to be understood by > > > applicat...

...a comments like V1. What's the advantage of inventing a new protocol? > > I'm trying to make it work in VFIO's way.. > > > > > I believe either of the following should be better: > > > > > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > > > extend it with e.g notify region. The advantages is that all exist userspace > > > program could be reused without modification (or minimal modification). And > > > vhost API hides lots of details that is not necessary to be understood by > > > applicat...

...quests in above structure. > > > Still a comments like V1. What's the advantage of inventing a new protocol? I'm trying to make it work in VFIO's way.. > I believe either of the following should be better: > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > extend it with e.g notify region. The advantages is that all exist userspace > program could be reused without modification (or minimal modification). And > vhost API hides lots of details that is not necessary to be understood by > application (e.g in the case of container). Do...

...quests in above structure. > > > Still a comments like V1. What's the advantage of inventing a new protocol? I'm trying to make it work in VFIO's way.. > I believe either of the following should be better: > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > extend it with e.g notify region. The advantages is that all exist userspace > program could be reused without modification (or minimal modification). And > vhost API hides lots of details that is not necessary to be understood by > application (e.g in the case of container). Do...

...> I'm trying to make it work in VFIO's way.. > > > > > > > > > > > > > I believe either of the following should be better: > > > > > > > > > > > > > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > > > > > > > extend it with e.g notify region. The advantages is that all exist userspace > > > > > > > program could be reused without modification (or minimal modification). And > > > > > > > vhost API hides lots of details that...

...> I'm trying to make it work in VFIO's way.. > > > > > > > > > > > > > I believe either of the following should be better: > > > > > > > > > > > > > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > > > > > > > extend it with e.g notify region. The advantages is that all exist userspace > > > > > > > program could be reused without modification (or minimal modification). And > > > > > > > vhost API hides lots of details that...

...t; I'm trying to make it work in VFIO's way.. > > > > > > > > > > > > > I believe either of the following should be better: > > > > > > > > > > > > > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > > > > > > > extend it with e.g notify region. The advantages is that all exist userspace > > > > > > > program could be reused without modification (or minimal modification). And > > > > > > > vhost API hides lots of details that...

...t; I'm trying to make it work in VFIO's way.. > > > > > > > > > > > > > I believe either of the following should be better: > > > > > > > > > > > > > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > > > > > > > extend it with e.g notify region. The advantages is that all exist userspace > > > > > > > program could be reused without modification (or minimal modification). And > > > > > > > vhost API hides lots of details that...

...). This makes the API less flexibile. The reason is we store the irq in vhost-vdpa not vDPA. I wonder whether the following looks better: 1) store irq in vdpa device 2) register producer when DRIVER_OK and unregister producer when !DRIVER_OK in vhost-vDPA 3) deal with the synchronization with SET_VRING_CALL 4) document that irq is not expected to be changed during DRIVER_OK This can make sure the API works during driver probe, and we don't need the setup_irq and unsetup_irq method in vdpa_driver Thanks > + */ > +int vdpa_devm_request_irq(struct device *dev, struct vdpa_device *vdev, &gt...

...s like V1. What's the advantage of inventing a new protocol? >>> I'm trying to make it work in VFIO's way.. >>> >>>> I believe either of the following should be better: >>>> >>>> - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and >>>> extend it with e.g notify region. The advantages is that all exist userspace >>>> program could be reused without modification (or minimal modification). And >>>> vhost API hides lots of details that is not necessary to be understood by >>>>...

...nventing a new protocol? >>>>> I'm trying to make it work in VFIO's way.. >>>>> >>>>>> I believe either of the following should be better: >>>>>> >>>>>> - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and >>>>>> extend it with e.g notify region. The advantages is that all exist userspace >>>>>> program could be reused without modification (or minimal modification). And >>>>>> vhost API hides lots of details that is not necessary to be underst...

...cture. >> >> Still a comments like V1. What's the advantage of inventing a new protocol? > I'm trying to make it work in VFIO's way.. > >> I believe either of the following should be better: >> >> - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and >> extend it with e.g notify region. The advantages is that all exist userspace >> program could be reused without modification (or minimal modification). And >> vhost API hides lots of details that is not necessary to be understood by >> application (e.g in the case of...

...> I'm trying to make it work in VFIO's way.. > > > > > > > > > I believe either of the following should be better: > > > > > > > > > > > > > > > > > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > > > > > > > > > extend it with e.g notify region. The advantages is that all exist userspace > > > > > > > > > program could be reused without modification (or minimal modification). And > > > > > > > > > vhost A...

...> I'm trying to make it work in VFIO's way.. > > > > > > > > > I believe either of the following should be better: > > > > > > > > > > > > > > > > > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > > > > > > > > > extend it with e.g notify region. The advantages is that all exist userspace > > > > > > > > > program could be reused without modification (or minimal modification). And > > > > > > > > > vhost A...

...;>>> I'm trying to make it work in VFIO's way.. >>>>>>> >>>>>>>> I believe either of the following should be better: >>>>>>>> >>>>>>>> - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and >>>>>>>> extend it with e.g notify region. The advantages is that all exist userspace >>>>>>>> program could be reused without modification (or minimal modification). And >>>>>>>> vhost API hides lots of details that is not...

...functions for setup/unsetup > and update irq offloading respectively by register/unregister > and re-register the irq_bypass_producer. > > With these functions, this commit can setup/unsetup > irq offloading through setting DRIVER_OK/!DRIVER_OK, and > update irq offloading through SET_VRING_CALL. > > Signed-off-by: Zhu Lingshan <lingshan.zhu at intel.com> > Suggested-by: Jason Wang <jasowang at redhat.com> > --- > drivers/vhost/Kconfig | 1 + > drivers/vhost/vdpa.c | 79 ++++++++++++++++++++++++++++++++++++++++++- > 2 files changed, 79 insertions(+),...

...t; > > > > I'm trying to make it work in VFIO's way.. > > > > > > > > > > > I believe either of the following should be better: > > > > > > > > > > > > - using vhost ioctl,? we can start from SET_VRING_KICK/SET_VRING_CALL and > > > > > > extend it with e.g notify region. The advantages is that all exist userspace > > > > > > program could be reused without modification (or minimal modification). And > > > > > > vhost API hides lots of details that is not necessar...

...functions for setup/unsetup > and update irq offloading respectively by register/unregister > and re-register the irq_bypass_producer. > > With these functions, this commit can setup/unsetup > irq offloading through setting DRIVER_OK/!DRIVER_OK, and > update irq offloading through SET_VRING_CALL. > > Signed-off-by: Zhu Lingshan <lingshan.zhu at intel.com> > Suggested-by: Jason Wang <jasowang at redhat.com> > --- > drivers/vhost/Kconfig | 1 + > drivers/vhost/vdpa.c | 79 ++++++++++++++++++++++++++++++++++++++++++- > 2 files changed, 79 insertions(+),...