From: Eugenio Perez Martin <eperezma@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: qemu-devel@nongnu.org, si-wei.liu@oracle.com,
qemu-stable@nongnu.org, Hawkins Jiawei <yin31149@gmail.com>
Subject: Re: [PATCH] vdpa: set old virtio status at cvq isolation probing end
Date: Wed, 26 Jul 2023 08:27:06 +0200 [thread overview]
Message-ID: <CAJaqyWeCNdmZX_iNywHxiD3fG39k5bRPOD2U13cmevbcUct+hA@mail.gmail.com> (raw)
In-Reply-To: <CACGkMEsqbZNGKdK1kM-qQeZShNeonQKK4_65vtCueQxUsRFTsQ@mail.gmail.com>
On Wed, Jul 26, 2023 at 4:07 AM Jason Wang <jasowang@redhat.com> wrote:
>
> On Wed, Jul 26, 2023 at 2:21 AM Eugenio Pérez <eperezma@redhat.com> wrote:
> >
> > The device already has a virtio status set by vhost_vdpa_init by the
> > time vhost_vdpa_probe_cvq_isolation is called. vhost_vdpa_init set
> > S_ACKNOWLEDGE and S_DRIVER, so it is invalid to just reset it.
> >
> > It is invalid to start the device after it, but all devices seems to be
> > fine with it. Fixing qemu so it follows virtio start procedure.
> >
> > Fixes: 152128d64697 ("vdpa: move CVQ isolation check to net_init_vhost_vdpa")
> > Reported-by: Dragos Tatulea <dtatulea@nvidia.com>
> > Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
> > ---
> > net/vhost-vdpa.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/net/vhost-vdpa.c b/net/vhost-vdpa.c
> > index 9795306742..d7e2b714b4 100644
> > --- a/net/vhost-vdpa.c
> > +++ b/net/vhost-vdpa.c
> > @@ -1333,6 +1333,8 @@ static int vhost_vdpa_probe_cvq_isolation(int device_fd, uint64_t features,
> > out:
> > status = 0;
> > ioctl(device_fd, VHOST_VDPA_SET_STATUS, &status);
> > + status = VIRTIO_CONFIG_S_ACKNOWLEDGE | VIRTIO_CONFIG_S_DRIVER;
> > + ioctl(device_fd, VHOST_VDPA_SET_STATUS, &status);
>
> So if we fail after FEATURES_OK, this basically clears that bit. Spec
> doesn't say it can or not, I wonder if a reset is better?
>
I don't follow this, the reset is just above the added code, isn't it?
> Btw, spec requires a read of status after setting FEATURES_OK, this
> seems to be missed in the current code.
>
I'm ok with that, but this patch does not touch that part.
To fix this properly we should:
- Expose vhost_vdpa_set_dev_features_fd as we did in previous versions
of the series that added vhost_vdpa_probe_cvq_isolation [1].
- Get status after vhost_vdpa_add_status, so both vhost start code and
this follows the standard properly.
Is it ok to do these on top of this patch?
Thanks!
[1] https://lore.kernel.org/qemu-devel/20230509154435.1410162-4-eperezma@redhat.com/
> Thanks
>
> > return r;
> > }
> >
> > --
> > 2.39.3
> >
>
next prev parent reply other threads:[~2023-07-26 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230725182143.1523091-1-eperezma@redhat.com>
2023-07-26 2:07 ` [PATCH] vdpa: set old virtio status at cvq isolation probing end Jason Wang
2023-07-26 6:27 ` Eugenio Perez Martin [this message]
2023-07-31 6:35 ` Jason Wang
2023-07-31 8:04 ` Eugenio Perez Martin
2023-07-31 8:42 ` Jason Wang
2023-07-31 9:40 ` Eugenio Perez Martin
2023-08-01 3:28 ` Jason Wang
2023-08-02 2:34 ` Jason Wang
2024-02-17 9:17 ` Michael Tokarev
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=CAJaqyWeCNdmZX_iNywHxiD3fG39k5bRPOD2U13cmevbcUct+hA@mail.gmail.com \
--to=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=si-wei.liu@oracle.com \
--cc=yin31149@gmail.com \
/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).