From: Jason Wang <jasowang@redhat.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: eric.auger.pro@gmail.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, peter.maydell@linaro.org, mst@redhat.com,
imammedo@redhat.com, peterx@redhat.com,
alex.williamson@redhat.com, clg@redhat.com, philmd@linaro.org,
zhenzhong.duan@intel.com, ddutile@redhat.com
Subject: Re: [PATCH v2 2/5] hw/i386/intel-iommu: Migrate to 3-phase reset
Date: Tue, 18 Feb 2025 09:14:23 +0800 [thread overview]
Message-ID: <CACGkMEst7Q5Zdu3AahgKaTnCh46b+-8f+wkFx0e3Apc+jSKRGw@mail.gmail.com> (raw)
In-Reply-To: <20250217133746.6801-3-eric.auger@redhat.com>
On Mon, Feb 17, 2025 at 9:38 PM Eric Auger <eric.auger@redhat.com> wrote:
>
> Currently the IOMMU may be reset before the devices
> it protects. For example this happens with virtio devices
> but also with VFIO devices. In this latter case this
> produces spurious translation faults on host.
>
> Let's use 3-phase reset mechanism and reset the IOMMU on
> exit phase after all DMA capable devices have been reset
> on 'enter' or 'hold' phase.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
Acked-by: Jason Wang <jasowang@redhat.com>
Thanks
next prev parent reply other threads:[~2025-02-18 1:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 13:36 [PATCH v2 0/5] Fix vIOMMU reset order Eric Auger
2025-02-17 13:36 ` [PATCH v2 1/5] hw/virtio/virtio-iommu: Migrate to 3-phase reset Eric Auger
2025-02-18 1:14 ` Jason Wang
2025-02-17 13:36 ` [PATCH v2 2/5] hw/i386/intel-iommu: " Eric Auger
2025-02-18 1:14 ` Jason Wang [this message]
2025-02-17 13:36 ` [PATCH v2 3/5] hw/arm/smmuv3: Move reset to exit phase Eric Auger
2025-02-17 13:36 ` [PATCH v2 4/5] hw/vfio/common: Add a trace point in vfio_reset_handler Eric Auger
2025-02-17 13:36 ` [PATCH v2 5/5] docs/devel/reset: Document reset expectations for DMA and IOMMU Eric Auger
2025-02-18 3:32 ` [PATCH v2 0/5] Fix vIOMMU reset order Duan, Zhenzhong
2025-02-18 7:24 ` Eric Auger
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=CACGkMEst7Q5Zdu3AahgKaTnCh46b+-8f+wkFx0e3Apc+jSKRGw@mail.gmail.com \
--to=jasowang@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=ddutile@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).