Displaying 3 results from an estimated 3 matches for "ring_access_after_kick".
2023 Jul 03
0
[PATCH] vdpa: reject F_ENABLE_AFTER_DRIVER_OK if backend does not support it
...: accept VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK backend feature")
> Signed-off-by: Eugenio P?rez <eperezma at redhat.com>
Please do send v3. And again, I don't want to send "after driver ok" hack
upstream at all, I merged it in next just to give it some testing.
We want RING_ACCESS_AFTER_KICK or some such.
> ---
> Sent with Fixes: tag pointing to git.kernel.org/pub/scm/linux/kernel/git/mst
> commit. Please let me know if I should send a v3 of [1] instead.
>
> [1] https://lore.kernel.org/lkml/20230609121244-mutt-send-email-mst at kernel.org/T/
> ---
> drivers/vho...
2023 Jul 04
1
[PATCH] vdpa: reject F_ENABLE_AFTER_DRIVER_OK if backend does not support it
...ackend feature")
> > > Signed-off-by: Eugenio P?rez <eperezma at redhat.com>
> >
> > Please do send v3. And again, I don't want to send "after driver ok" hack
> > upstream at all, I merged it in next just to give it some testing.
> > We want RING_ACCESS_AFTER_KICK or some such.
> >
>
> Current devices do not support that semantic.
Which devices specifically access the ring after DRIVER_OK but before
a kick?
> My plan was to convert
> it in vp_vdpa if needed, and reuse the current vdpa ops. Sorry if I
> was not explicit enough.
>
&...
2023 Jul 04
1
[PATCH] vdpa: reject F_ENABLE_AFTER_DRIVER_OK if backend does not support it
...ned-off-by: Eugenio P?rez <eperezma at redhat.com>
> > > >
> > > > Please do send v3. And again, I don't want to send "after driver ok" hack
> > > > upstream at all, I merged it in next just to give it some testing.
> > > > We want RING_ACCESS_AFTER_KICK or some such.
> > > >
> > >
> > > Current devices do not support that semantic.
> >
> > Which devices specifically access the ring after DRIVER_OK but before
> > a kick?
> >
>
> Previous versions of the QEMU LM series did a spurious kick...