From: Jason Wang <jasowang@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>
Cc: qemu-devel@nongnu.org, Parav Pandit <parav@mellanox.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
longpeng2@huawei.com, Stefano Garzarella <sgarzare@redhat.com>,
Gautam Dawar <gdawar@xilinx.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
Harpreet Singh Anand <hanand@xilinx.com>,
alvaro.karsz@solid-run.com,
Liuxiangdong <liuxiangdong5@huawei.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
si-wei.liu@oracle.com, Shannon Nelson <snelson@pensando.io>,
Lei Yang <leiyang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Laurent Vivier <lvivier@redhat.com>, Cindy Lu <lulu@redhat.com>
Subject: Re: [PATCH v3 2/5] vdpa: add vhost_vdpa_reset_status_fd
Date: Wed, 17 May 2023 11:14:28 +0800 [thread overview]
Message-ID: <CACGkMEufH7ZvJxKzbSXpv8G5RodKeh_WHj6iTe=YqG9pdp45nQ@mail.gmail.com> (raw)
In-Reply-To: <20230509154435.1410162-3-eperezma@redhat.com>
On Tue, May 9, 2023 at 11:44 PM Eugenio Pérez <eperezma@redhat.com> wrote:
>
> This allows to reset a vhost-vdpa device from external subsystems like
> vhost-net, since it does not have any struct vhost_dev by the time we
> need to use it.
>
> It is used in subsequent patches to negotiate features
> and probe for CVQ ASID isolation.
>
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
> ---
> include/hw/virtio/vhost-vdpa.h | 1 +
> hw/virtio/vhost-vdpa.c | 58 +++++++++++++++++++++++-----------
> 2 files changed, 41 insertions(+), 18 deletions(-)
>
> diff --git a/include/hw/virtio/vhost-vdpa.h b/include/hw/virtio/vhost-vdpa.h
> index c278a2a8de..28de7da91e 100644
> --- a/include/hw/virtio/vhost-vdpa.h
> +++ b/include/hw/virtio/vhost-vdpa.h
> @@ -54,6 +54,7 @@ typedef struct vhost_vdpa {
> VhostVDPAHostNotifier notifier[VIRTIO_QUEUE_MAX];
> } VhostVDPA;
>
> +void vhost_vdpa_reset_status_fd(int fd);
> int vhost_vdpa_get_iova_range(int fd, struct vhost_vdpa_iova_range *iova_range);
>
> int vhost_vdpa_dma_map(struct vhost_vdpa *v, uint32_t asid, hwaddr iova,
> diff --git a/hw/virtio/vhost-vdpa.c b/hw/virtio/vhost-vdpa.c
> index bbabea18f3..7a2053b8d9 100644
> --- a/hw/virtio/vhost-vdpa.c
> +++ b/hw/virtio/vhost-vdpa.c
> @@ -335,38 +335,45 @@ static const MemoryListener vhost_vdpa_memory_listener = {
> .region_del = vhost_vdpa_listener_region_del,
> };
>
> -static int vhost_vdpa_call(struct vhost_dev *dev, unsigned long int request,
> - void *arg)
> +static int vhost_vdpa_dev_fd(const struct vhost_dev *dev)
> {
> struct vhost_vdpa *v = dev->opaque;
> - int fd = v->device_fd;
> - int ret;
>
> assert(dev->vhost_ops->backend_type == VHOST_BACKEND_TYPE_VDPA);
> + return v->device_fd;
> +}
Nit: unless the vhost_dev structure is opaque to the upper layer, I
don't see any advantage for having a dedicated indirect helper to get
device_fd.
> +
> +static int vhost_vdpa_call_fd(int fd, unsigned long int request, void *arg)
> +{
> + int ret = ioctl(fd, request, arg);
>
> - ret = ioctl(fd, request, arg);
> return ret < 0 ? -errno : ret;
> }
>
> -static int vhost_vdpa_add_status(struct vhost_dev *dev, uint8_t status)
> +static int vhost_vdpa_call(struct vhost_dev *dev, unsigned long int request,
> + void *arg)
> +{
> + return vhost_vdpa_call_fd(vhost_vdpa_dev_fd(dev), request, arg);
> +}
> +
> +static int vhost_vdpa_add_status_fd(int fd, uint8_t status)
> {
> uint8_t s;
> int ret;
>
> - trace_vhost_vdpa_add_status(dev, status);
> - ret = vhost_vdpa_call(dev, VHOST_VDPA_GET_STATUS, &s);
> + ret = vhost_vdpa_call_fd(fd, VHOST_VDPA_GET_STATUS, &s);
> if (ret < 0) {
> return ret;
> }
>
> s |= status;
>
> - ret = vhost_vdpa_call(dev, VHOST_VDPA_SET_STATUS, &s);
> + ret = vhost_vdpa_call_fd(fd, VHOST_VDPA_SET_STATUS, &s);
> if (ret < 0) {
> return ret;
> }
>
> - ret = vhost_vdpa_call(dev, VHOST_VDPA_GET_STATUS, &s);
> + ret = vhost_vdpa_call_fd(fd, VHOST_VDPA_GET_STATUS, &s);
> if (ret < 0) {
> return ret;
> }
> @@ -378,6 +385,12 @@ static int vhost_vdpa_add_status(struct vhost_dev *dev, uint8_t status)
> return 0;
> }
>
> +static int vhost_vdpa_add_status(struct vhost_dev *dev, uint8_t status)
> +{
> + trace_vhost_vdpa_add_status(dev, status);
> + return vhost_vdpa_add_status_fd(vhost_vdpa_dev_fd(dev), status);
> +}
> +
> int vhost_vdpa_get_iova_range(int fd, struct vhost_vdpa_iova_range *iova_range)
> {
> int ret = ioctl(fd, VHOST_VDPA_GET_IOVA_RANGE, iova_range);
> @@ -709,16 +722,20 @@ static int vhost_vdpa_get_device_id(struct vhost_dev *dev,
> return ret;
> }
>
> +static int vhost_vdpa_reset_device_fd(int fd)
> +{
> + uint8_t status = 0;
> +
> + return vhost_vdpa_call_fd(fd, VHOST_VDPA_SET_STATUS, &status);
> +}
> +
> static int vhost_vdpa_reset_device(struct vhost_dev *dev)
> {
> struct vhost_vdpa *v = dev->opaque;
> - int ret;
> - uint8_t status = 0;
>
> - ret = vhost_vdpa_call(dev, VHOST_VDPA_SET_STATUS, &status);
> - trace_vhost_vdpa_reset_device(dev);
> v->suspended = false;
> - return ret;
> + trace_vhost_vdpa_reset_device(dev);
> + return vhost_vdpa_reset_device_fd(vhost_vdpa_dev_fd(dev));
> }
>
> static int vhost_vdpa_get_vq_index(struct vhost_dev *dev, int idx)
> @@ -1170,6 +1187,13 @@ static int vhost_vdpa_dev_start(struct vhost_dev *dev, bool started)
> return 0;
> }
>
> +void vhost_vdpa_reset_status_fd(int fd)
> +{
> + vhost_vdpa_reset_device_fd(fd);
> + vhost_vdpa_add_status_fd(fd, VIRTIO_CONFIG_S_ACKNOWLEDGE |
> + VIRTIO_CONFIG_S_DRIVER);
I would like to rename this function since it does more than just reset.
Thanks
> +}
> +
> static void vhost_vdpa_reset_status(struct vhost_dev *dev)
> {
> struct vhost_vdpa *v = dev->opaque;
> @@ -1178,9 +1202,7 @@ static void vhost_vdpa_reset_status(struct vhost_dev *dev)
> return;
> }
>
> - vhost_vdpa_reset_device(dev);
> - vhost_vdpa_add_status(dev, VIRTIO_CONFIG_S_ACKNOWLEDGE |
> - VIRTIO_CONFIG_S_DRIVER);
> + vhost_vdpa_reset_status_fd(vhost_vdpa_dev_fd(dev));
> memory_listener_unregister(&v->listener);
> }
>
> --
> 2.31.1
>
next prev parent reply other threads:[~2023-05-17 3:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 15:44 [PATCH v3 0/5] Move ASID test to vhost-vdpa net initialization Eugenio Pérez
2023-05-09 15:44 ` [PATCH v3 1/5] vdpa: Remove status in reset tracing Eugenio Pérez
2023-05-09 15:44 ` [PATCH v3 2/5] vdpa: add vhost_vdpa_reset_status_fd Eugenio Pérez
2023-05-17 3:14 ` Jason Wang [this message]
2023-05-17 5:46 ` Eugenio Perez Martin
2023-05-17 5:49 ` Jason Wang
2023-05-24 17:36 ` Eugenio Perez Martin
2023-05-26 4:10 ` Jason Wang
2023-05-09 15:44 ` [PATCH v3 3/5] vdpa: add vhost_vdpa_set_dev_features_fd Eugenio Pérez
2023-05-09 15:44 ` [PATCH v3 4/5] vdpa: return errno in vhost_vdpa_get_vring_group error Eugenio Pérez
2023-05-09 15:44 ` [PATCH v3 5/5] vdpa: move CVQ isolation check to net_init_vhost_vdpa Eugenio Pérez
2023-05-17 3:59 ` Jason Wang
2023-05-17 6:29 ` Eugenio Perez Martin
2023-05-18 5:49 ` Jason Wang
2023-05-18 6:36 ` Eugenio Perez Martin
2023-05-18 6:58 ` Jason Wang
2023-05-18 21:22 ` Michael S. Tsirkin
2023-05-19 4:50 ` Eugenio Perez Martin
2023-05-17 6:18 ` [PATCH v3 0/5] Move ASID test to vhost-vdpa net initialization Lei Yang
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='CACGkMEufH7ZvJxKzbSXpv8G5RodKeh_WHj6iTe=YqG9pdp45nQ@mail.gmail.com' \
--to=jasowang@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=arei.gonglei@huawei.com \
--cc=dtatulea@nvidia.com \
--cc=eperezma@redhat.com \
--cc=gdawar@xilinx.com \
--cc=hanand@xilinx.com \
--cc=leiyang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=liuxiangdong5@huawei.com \
--cc=longpeng2@huawei.com \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=si-wei.liu@oracle.com \
--cc=snelson@pensando.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).