From: "Eugenio Pérez" <eperezma@redhat.com>
To: virtualization@lists.linux-foundation.org,
Jason Wang <jasowang@redhat.com>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Stefano Garzarella <sgarzare@redhat.com>,
Longpeng <longpeng2@huawei.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
martinh@xilinx.com, hanand@xilinx.com,
Si-Wei Liu <si-wei.liu@oracle.com>,
dinang@xilinx.com, Eli Cohen <elic@nvidia.com>,
lvivier@redhat.com, pabloc@xilinx.com, gautam.dawar@amd.com,
Xie Yongji <xieyongji@bytedance.com>,
habetsm.xilinx@gmail.com,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
tanuj.kamde@amd.com, eperezma@redhat.com,
Wu Zongyong <wuzongyong@linux.alibaba.com>,
martinpo@xilinx.com, lulu@redhat.com, ecree.xilinx@gmail.com,
Parav Pandit <parav@nvidia.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Zhang Min <zhang.min9@zte.com.cn>
Subject: [PATCH 0/4] Implement vdpasim stop operation
Date: Fri, 20 May 2022 19:23:21 +0200 [thread overview]
Message-ID: <20220520172325.980884-1-eperezma@redhat.com> (raw)
Implement stop operation for vdpa_sim devices, so vhost-vdpa will offer
that backend feature and userspace can effectively stop the device.
This is a must before get virtqueue indexes (base) for live migration,
since the device could modify them after userland gets them. There are
individual ways to perform that action for some devices
(VHOST_NET_SET_BACKEND, VHOST_VSOCK_SET_RUNNING, ...) but there was no
way to perform it for any vhost device (and, in particular, vhost-vdpa).
Comments are welcome.
Eugenio Pérez (4):
vdpa: Add stop operation
vhost-vdpa: introduce STOP backend feature bit
vhost-vdpa: uAPI to stop the device
vdpa_sim: Implement stop vdpa op
drivers/vdpa/vdpa_sim/vdpa_sim.c | 21 +++++++++++++++++++
drivers/vdpa/vdpa_sim/vdpa_sim.h | 1 +
drivers/vdpa/vdpa_sim/vdpa_sim_net.c | 3 +++
drivers/vhost/vdpa.c | 31 ++++++++++++++++++++++++++++
include/linux/vdpa.h | 6 ++++++
include/uapi/linux/vhost.h | 3 +++
include/uapi/linux/vhost_types.h | 2 ++
7 files changed, 67 insertions(+)
--
2.27.0
next reply other threads:[~2022-05-20 17:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 17:23 Eugenio Pérez [this message]
2022-05-20 17:23 ` [PATCH 1/4] vdpa: Add stop operation Eugenio Pérez
2022-05-21 10:13 ` Si-Wei Liu
2022-05-21 10:13 ` Si-Wei Liu
2022-05-23 19:20 ` Eugenio Perez Martin
2022-05-23 23:54 ` Si-Wei Liu
2022-05-23 23:54 ` Si-Wei Liu
2022-05-24 0:01 ` Si-Wei Liu
2022-05-24 0:01 ` Si-Wei Liu
2022-05-24 2:45 ` Jason Wang
2022-05-24 2:45 ` Jason Wang
2022-05-24 7:38 ` Eugenio Perez Martin
2022-05-24 7:09 ` Stefano Garzarella
2022-05-24 7:09 ` Stefano Garzarella
2022-05-24 7:42 ` Eugenio Perez Martin
2022-05-24 7:51 ` Stefano Garzarella
2022-05-24 7:51 ` Stefano Garzarella
2022-05-20 17:23 ` [PATCH 2/4] vhost-vdpa: introduce STOP backend feature bit Eugenio Pérez
2022-05-21 10:24 ` Si-Wei Liu
2022-05-21 10:24 ` Si-Wei Liu
2022-05-23 9:57 ` Eugenio Perez Martin
2022-05-20 17:23 ` [PATCH 3/4] vhost-vdpa: uAPI to stop the device Eugenio Pérez
2022-05-21 5:20 ` kernel test robot
2022-05-21 5:20 ` kernel test robot
2022-05-21 8:36 ` Martin Habets
2022-05-23 8:11 ` Eugenio Perez Martin
2022-05-20 17:23 ` [PATCH 4/4] vdpa_sim: Implement stop vdpa op Eugenio Pérez
2022-05-23 8:27 ` Stefano Garzarella
2022-05-23 8:27 ` Stefano Garzarella
2022-05-23 19:07 ` Eugenio Perez Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220520172325.980884-1-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dan.carpenter@oracle.com \
--cc=dinang@xilinx.com \
--cc=ecree.xilinx@gmail.com \
--cc=elic@nvidia.com \
--cc=gautam.dawar@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=hanand@xilinx.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--cc=martinh@xilinx.com \
--cc=martinpo@xilinx.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabloc@xilinx.com \
--cc=parav@nvidia.com \
--cc=sgarzare@redhat.com \
--cc=si-wei.liu@oracle.com \
--cc=tanuj.kamde@amd.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wuzongyong@linux.alibaba.com \
--cc=xieyongji@bytedance.com \
--cc=zhang.min9@zte.com.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.