netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eli Cohen <elic@nvidia.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Si-Wei Liu <siwliu.kernel@gmail.com>, <jasowang@redhat.com>,
	<netdev@vger.kernel.org>, <joao.m.martins@oracle.com>,
	<boris.ostrovsky@oracle.com>, <linux-kernel@vger.kernel.org>,
	<virtualization@lists.linux-foundation.org>,
	Si-Wei Liu <si-wei.liu@oracle.com>
Subject: Re: [PATCH] vdpa/mlx5: should keep avail_index despite device status
Date: Tue, 6 Oct 2020 09:42:51 +0300	[thread overview]
Message-ID: <20201006064251.GA245562@mtl-vdi-166.wap.labs.mlnx> (raw)
In-Reply-To: <20201006022133-mutt-send-email-mst@kernel.org>

On Tue, Oct 06, 2020 at 02:22:15AM -0400, Michael S. Tsirkin wrote:

Acked-by: Eli Cohen <elic@nvidia.com>

> On Fri, Oct 02, 2020 at 01:17:00PM -0700, Si-Wei Liu wrote:
> > + Eli.
> > 
> > On Thu, Oct 1, 2020 at 2:02 PM Si-Wei Liu <si-wei.liu@oracle.com> wrote:
> > >
> > > A VM with mlx5 vDPA has below warnings while being reset:
> > >
> > > vhost VQ 0 ring restore failed: -1: Resource temporarily unavailable (11)
> > > vhost VQ 1 ring restore failed: -1: Resource temporarily unavailable (11)
> > >
> > > We should allow userspace emulating the virtio device be
> > > able to get to vq's avail_index, regardless of vDPA device
> > > status. Save the index that was last seen when virtq was
> > > stopped, so that userspace doesn't complain.
> > >
> > > Signed-off-by: Si-Wei Liu <si-wei.liu@oracle.com>
> 
> Eli can you review this pls? I need to send a pull request to Linux by
> tomorrow - do we want to include this?
> 
> > > ---
> > >  drivers/vdpa/mlx5/net/mlx5_vnet.c | 20 ++++++++++++++------
> > >  1 file changed, 14 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/drivers/vdpa/mlx5/net/mlx5_vnet.c b/drivers/vdpa/mlx5/net/mlx5_vnet.c
> > > index 70676a6..74264e59 100644
> > > --- a/drivers/vdpa/mlx5/net/mlx5_vnet.c
> > > +++ b/drivers/vdpa/mlx5/net/mlx5_vnet.c
> > > @@ -1133,15 +1133,17 @@ static void suspend_vq(struct mlx5_vdpa_net *ndev, struct mlx5_vdpa_virtqueue *m
> > >         if (!mvq->initialized)
> > >                 return;
> > >
> > > -       if (query_virtqueue(ndev, mvq, &attr)) {
> > > -               mlx5_vdpa_warn(&ndev->mvdev, "failed to query virtqueue\n");
> > > -               return;
> > > -       }
> > >         if (mvq->fw_state != MLX5_VIRTIO_NET_Q_OBJECT_STATE_RDY)
> > >                 return;
> > >
> > >         if (modify_virtqueue(ndev, mvq, MLX5_VIRTIO_NET_Q_OBJECT_STATE_SUSPEND))
> > >                 mlx5_vdpa_warn(&ndev->mvdev, "modify to suspend failed\n");
> > > +
> > > +       if (query_virtqueue(ndev, mvq, &attr)) {
> > > +               mlx5_vdpa_warn(&ndev->mvdev, "failed to query virtqueue\n");
> > > +               return;
> > > +       }
> > > +       mvq->avail_idx = attr.available_index;
> > >  }
> > >
> > >  static void suspend_vqs(struct mlx5_vdpa_net *ndev)
> > > @@ -1411,8 +1413,14 @@ static int mlx5_vdpa_get_vq_state(struct vdpa_device *vdev, u16 idx, struct vdpa
> > >         struct mlx5_virtq_attr attr;
> > >         int err;
> > >
> > > -       if (!mvq->initialized)
> > > -               return -EAGAIN;
> > > +       /* If the virtq object was destroyed, use the value saved at
> > > +        * the last minute of suspend_vq. This caters for userspace
> > > +        * that cares about emulating the index after vq is stopped.
> > > +        */
> > > +       if (!mvq->initialized) {
> > > +               state->avail_index = mvq->avail_idx;
> > > +               return 0;
> > > +       }
> > >
> > >         err = query_virtqueue(ndev, mvq, &attr);
> > >         if (err) {
> > > --
> > > 1.8.3.1
> > >
> 

  reply	other threads:[~2020-10-06  6:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 20:18 [PATCH] vdpa/mlx5: should keep avail_index despite device status Si-Wei Liu
2020-10-02 20:17 ` Si-Wei Liu
2020-10-06  6:22   ` Michael S. Tsirkin
2020-10-06  6:42     ` Eli Cohen [this message]
2020-10-10  7:31 ` 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=20201006064251.GA245562@mtl-vdi-166.wap.labs.mlnx \
    --to=elic@nvidia.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jasowang@redhat.com \
    --cc=joao.m.martins@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=si-wei.liu@oracle.com \
    --cc=siwliu.kernel@gmail.com \
    --cc=virtualization@lists.linux-foundation.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).