[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230609092127.170673-1-eperezma@redhat.com>
Date: Fri, 9 Jun 2023 11:21:23 +0200
From: Eugenio Pérez <eperezma@...hat.com>
To: mst@...hat.com, Jason Wang <jasowang@...hat.com>
Cc: Zhu Lingshan <lingshan.zhu@...el.com>,
virtualization@...ts.linux-foundation.org,
"Gonglei (Arei)" <arei.gonglei@...wei.com>, longpeng2@...wei.com,
Lei Yang <leiyang@...hat.com>,
Parav Pandit <parav@...lanox.com>,
Gautam Dawar <gdawar@...inx.com>,
Dragos Tatulea <dtatulea@...dia.com>,
Laurent Vivier <lvivier@...hat.com>, linux-api@...r.kernel.org,
Liuxiangdong <liuxiangdong5@...wei.com>,
linux-kernel@...r.kernel.org, alvaro.karsz@...id-run.com,
Shannon Nelson <snelson@...sando.io>,
Stefano Garzarella <sgarzare@...hat.com>,
Cindy Lu <lulu@...hat.com>, si-wei.liu@...cle.com,
Harpreet Singh Anand <hanand@...inx.com>
Subject: [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(-)
--
2.31.1
Powered by blists - more mailing lists