qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@redhat.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>, qemu-devel@nongnu.org
Cc: mst@redhat.com, jean-philippe@linaro.org
Subject: Re: [PATCH] virtio-iommu: Fix migration regression
Date: Mon, 27 Jun 2022 18:31:39 +0200	[thread overview]
Message-ID: <5b75ba05-4cb3-7812-fc86-ed1a7e2cbb39@redhat.com> (raw)
In-Reply-To: <20220624093740.3525267-1-zhenzhong.duan@intel.com>

Hi,

On 6/24/22 11:37, Zhenzhong Duan wrote:
> We also need to switch to the right address space on dest side
> after loading the device status. DMA to wrong address space is
> destructive.
>
> Fixes: 3facd774962fd ("virtio-iommu: Add bypass mode support to assigned device")
> Suggested-by: Eric Auger <eric.auger@redhat.com>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
Reviewed-by: Eric Auger <eric.auger@redhat.com>

Eric
> ---
>  hw/virtio/virtio-iommu.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
>
> diff --git a/hw/virtio/virtio-iommu.c b/hw/virtio/virtio-iommu.c
> index 08b227e828f8..281152d338f4 100644
> --- a/hw/virtio/virtio-iommu.c
> +++ b/hw/virtio/virtio-iommu.c
> @@ -1322,6 +1322,14 @@ static int iommu_post_load(void *opaque, int version_id)
>      VirtIOIOMMU *s = opaque;
>  
>      g_tree_foreach(s->domains, reconstruct_endpoints, s);
> +
> +    /*
> +     * Memory regions are dynamically turned on/off depending on
> +     * 'config.bypass' and attached domain type if there is. After
> +     * migration, we need to make sure the memory regions are
> +     * still correct.
> +     */
> +    virtio_iommu_switch_address_space_all(s);
>      return 0;
>  }
>  



      reply	other threads:[~2022-06-27 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  9:37 [PATCH] virtio-iommu: Fix migration regression Zhenzhong Duan
2022-06-27 16:31 ` Eric Auger [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=5b75ba05-4cb3-7812-fc86-ed1a7e2cbb39@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=jean-philippe@linaro.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhenzhong.duan@intel.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).