qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Cindy Lu <lulu@redhat.com>, mst@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 2/5] vhost_net: enable configure interrupt when vhost_net start
Date: Wed, 27 Jan 2021 13:38:09 +0800	[thread overview]
Message-ID: <6d276606-e4d7-e2ee-3fa6-ab1010c84093@redhat.com> (raw)
In-Reply-To: <20210126074254.3225-3-lulu@redhat.com>


On 2021/1/26 下午3:42, Cindy Lu wrote:
> While peer is vhost vdpa, setup the configure interrupt function
> vhost_net_start and release the resource when vhost_net_stop
>
> Signed-off-by: Cindy Lu <lulu@redhat.com>
> ---
>   hw/net/vhost_net.c | 19 ++++++++++++++++++-
>   1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git a/hw/net/vhost_net.c b/hw/net/vhost_net.c
> index 24d555e764..0660da474a 100644
> --- a/hw/net/vhost_net.c
> +++ b/hw/net/vhost_net.c
> @@ -345,6 +345,15 @@ int vhost_net_start(VirtIODevice *dev, NetClientState *ncs,
>           error_report("Error binding guest notifier: %d", -r);
>           goto err;
>       }
> +    if (ncs->peer && ncs->peer->info->type == NET_CLIENT_DRIVER_VHOST_VDPA) {
> +        if (k->set_config_notifiers) {
> +            r = k->set_config_notifiers(qbus->parent, true);
> +            if (r < 0) {
> +                error_report("Error binding config notifier: %d", -r);
> +                goto err;
> +            }
> +       }
> +    }
>   
>       for (i = 0; i < total_queues; i++) {
>           peer = qemu_get_peer(ncs, i);
> @@ -391,7 +400,15 @@ void vhost_net_stop(VirtIODevice *dev, NetClientState *ncs,
>       for (i = 0; i < total_queues; i++) {
>           vhost_net_stop_one(get_vhost_net(ncs[i].peer), dev);
>       }
> -
> +   if (ncs->peer && ncs->peer->info->type == NET_CLIENT_DRIVER_VHOST_VDPA) {
> +        if (k->set_config_notifiers) {


It looks to me that checking k->set_config_notifier is sufficient here.

Thanks


> +            r = k->set_config_notifiers(qbus->parent, false);
> +            if (r < 0) {
> +                error_report("Error unbinding config notifier: %d", -r);
> +            }
> +           assert(r >= 0);
> +        }
> +    }
>       r = k->set_guest_notifiers(qbus->parent, total_queues * 2, false);
>       if (r < 0) {
>           fprintf(stderr, "vhost guest notifier cleanup failed: %d\n", r);



  reply	other threads:[~2021-01-27  5:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26  7:42 [PATCH v3 0/5] vhost-vdpa: add support for configure interrupt Cindy Lu
2021-01-26  7:42 ` [PATCH v3 1/5] virtio: " Cindy Lu
2021-01-27  5:35   ` Jason Wang
2021-01-26  7:42 ` [PATCH v3 2/5] vhost_net: enable configure interrupt when vhost_net start Cindy Lu
2021-01-27  5:38   ` Jason Wang [this message]
2021-01-27  7:25     ` Cindy Lu
2021-01-26  7:42 ` [PATCH v3 3/5] virtio-pci: add support for configure interrupt Cindy Lu
2021-01-27  5:44   ` Jason Wang
2021-01-27  7:39     ` Cindy Lu
2021-01-26  7:42 ` [PATCH v3 4/5] virtio-mmio: " Cindy Lu
2021-01-26  7:42 ` [PATCH v3 5/5] vhost-vdpa: add callback function " Cindy Lu
2021-01-26 14:53   ` Stefano Garzarella
2021-01-27  2:51     ` Cindy Lu
2021-01-27  5:47   ` Jason Wang
2021-01-27  7:51     ` Cindy Lu
2021-01-27  8:16       ` Jason Wang

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=6d276606-e4d7-e2ee-3fa6-ab1010c84093@redhat.com \
    --to=jasowang@redhat.com \
    --cc=lulu@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).