All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugenio Perez Martin <eperezma@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] vdpa: do not save failed dma maps in SVQ iova tree
Date: Thu, 4 Aug 2022 17:50:50 +0200	[thread overview]
Message-ID: <CAJaqyWd0LM1Dfpm1LnBSgjcLOZ-ocLVLNGgWG=hpxtXmMwyi0g@mail.gmail.com> (raw)
In-Reply-To: <CAJaqyWebpuOcuud7F4KaQ3mmyf_4v6n4k9FJv_mzK0jVj2aVyA@mail.gmail.com>

On Thu, Aug 4, 2022 at 5:02 PM Eugenio Perez Martin <eperezma@redhat.com> wrote:
>
> On Thu, Aug 4, 2022 at 6:51 AM Jason Wang <jasowang@redhat.com> wrote:
> >
> >
> > 在 2022/8/3 16:12, Eugenio Perez Martin 写道:
> > > On Wed, Aug 3, 2022 at 10:09 AM Jason Wang <jasowang@redhat.com> wrote:
> > >> On Tue, Aug 2, 2022 at 10:39 PM Eugenio Pérez <eperezma@redhat.com> wrote:
> > >>> If a map fails for whatever reason, it must not be saved in the tree.
> > >>> Otherwise, qemu will try to unmap it in cleanup, leaving to more errors.
> > >>>
> > >>> Fixes: 34e3c94eda ("vdpa: Add custom IOTLB translations to SVQ")
> > >>> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
> > >>> ---
> > >>>   hw/virtio/vhost-vdpa.c | 20 +++++++++++++-------
> > >>>   1 file changed, 13 insertions(+), 7 deletions(-)
> > >>>
> > >>> diff --git a/hw/virtio/vhost-vdpa.c b/hw/virtio/vhost-vdpa.c
> > >>> index 3ff9ce3501..e44c23dce5 100644
> > >>> --- a/hw/virtio/vhost-vdpa.c
> > >>> +++ b/hw/virtio/vhost-vdpa.c
> > >>> @@ -176,6 +176,7 @@ static void vhost_vdpa_listener_commit(MemoryListener *listener)
> > >>>   static void vhost_vdpa_listener_region_add(MemoryListener *listener,
> > >>>                                              MemoryRegionSection *section)
> > >>>   {
> > >>> +    DMAMap mem_region = {};
> > >>>       struct vhost_vdpa *v = container_of(listener, struct vhost_vdpa, listener);
> > >>>       hwaddr iova;
> > >>>       Int128 llend, llsize;
> > >>> @@ -212,13 +213,13 @@ static void vhost_vdpa_listener_region_add(MemoryListener *listener,
> > >>>
> > >>>       llsize = int128_sub(llend, int128_make64(iova));
> > >>>       if (v->shadow_vqs_enabled) {
> > >>> -        DMAMap mem_region = {
> > >>> -            .translated_addr = (hwaddr)(uintptr_t)vaddr,
> > >>> -            .size = int128_get64(llsize) - 1,
> > >>> -            .perm = IOMMU_ACCESS_FLAG(true, section->readonly),
> > >>> -        };
> > >> Nit: can we keep this part unchanged?
> > >>
> > > We can, but that implies we should look for iova again at fail_map
> > > tag. If you are ok with that I'm fine to perform the search again.
> >
> >
> > I meant something like:
> >
> > diff --git a/hw/virtio/vhost-vdpa.c b/hw/virtio/vhost-vdpa.c
> > index 9a2daef7e3..edf40868e3 100644
> > --- a/hw/virtio/vhost-vdpa.c
> > +++ b/hw/virtio/vhost-vdpa.c
> > @@ -232,11 +232,15 @@ static void
> > vhost_vdpa_listener_region_add(MemoryListener *listener,
> >                                vaddr, section->readonly);
> >       if (ret) {
> >           error_report("vhost vdpa map fail!");
> > -        goto fail;
> > +        goto fail_unmap;
> >       }
> >
> >       return;
> >
> > +fail_unmap:
> > +    if (v->shadow_vqs_enabled) {
> > +        vhost_iova_tree_remove(v->iova_tree, &mem_region);
> > +    }
> >   fail:
> >       /*
> >        * On the initfn path, store the first error in the container so we
> >
>
> Sorry, still not following.
>
> mem_region does not exist in the error path, since it's declared in
> the if (v->shadow_vqs_enabled){} block. We can left first part
> unchanged if we do a lookup for the mem region, based on the
> translated addr.
>

Sending v2 expanding the fix without this comment, please let me know
ifI misunderstood something.

Thanks!



      reply	other threads:[~2022-08-04 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 14:39 [PATCH] vdpa: do not save failed dma maps in SVQ iova tree Eugenio Pérez
2022-08-02 14:48 ` Eugenio Perez Martin
2022-08-03  8:09 ` Jason Wang
2022-08-03  8:12   ` Eugenio Perez Martin
2022-08-04  4:51     ` Jason Wang
2022-08-04 15:02       ` Eugenio Perez Martin
2022-08-04 15:50         ` Eugenio Perez Martin [this message]

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='CAJaqyWd0LM1Dfpm1LnBSgjcLOZ-ocLVLNGgWG=hpxtXmMwyi0g@mail.gmail.com' \
    --to=eperezma@redhat.com \
    --cc=jasowang@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 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.