Skip to content

Add VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK flag to vdpa backend

Eugenio Pérez linux-api lkml virtualization 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v2 Latest4 patches 2 repliesIn review

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4vdpa: add VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK flaginclude/uapi/linux/vhost_types.h+4 -00 replies
2/4vdpa: accept VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK backend featuredrivers/vhost/vdpa.c+2 -12 replies
3/4vdpa: add get_backend_features vdpa operationdrivers/vhost/vdpa.c include/linux/vdpa.h+16 -00 replies
4/4vdpa_sim: offer VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OKdrivers/vdpa/vdpa_sim/vdpa_sim.c+8 -00 replies

Reviews trailers per patch

All 4 patches have a Reviewed-by or Acked-by.

PatchShannon Nelson
1/4A-b
2/4A-b
3/4A-b
4/4A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v2 thread

Cover letter [PATCH v2 0/4] Add VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK flag to vdpa backend

To migrate vDPA-net device state though CVQ we need to start the dataplane after the control virtqueue.

As vdpa frontend doesn't know if the parent vdpa driver supports it, let's allow them to expose custom backend features by themselves.

Comments are welcome.

Thanks!

v2: address doc issues from checkpath and fix lack of signed-off-by.

v1: from RFC: Tweak doc as Shannon suggestion.

Eugenio Pérez (4):
vdpa: add VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK flag
vdpa: accept VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK backend feature
vdpa: add get_backend_features vdpa operation
vdpa_sim: offer VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK

 drivers/vdpa/vdpa_sim/vdpa_sim.c |  8 ++++++++
 drivers/vhost/vdpa.c             | 15 ++++++++++++++-
 include/linux/vdpa.h             |  4 ++++
 include/uapi/linux/vhost_types.h |  4 ++++
 4 files changed, 30 insertions(+), 1 deletion(-)
Signature · 1 line
2.31.1