From: Eric Auger <eric.auger@redhat.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>, qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, clg@redhat.com,
joao.m.martins@oracle.com, chao.p.peng@intel.com
Subject: Re: [PATCH 0/2] Don't initialize HOST_IOMMU_DEVICE with mdev
Date: Mon, 22 Jul 2024 11:31:11 +0200 [thread overview]
Message-ID: <536dcece-a249-4fe6-977d-d970795dfbe2@redhat.com> (raw)
In-Reply-To: <20240722070713.1342711-1-zhenzhong.duan@intel.com>
Hi Zhenzhong,
On 7/22/24 09:07, Zhenzhong Duan wrote:
> This fixes a potential issue with mdev that fails to initialize HOST_IOMMU_DEVICE.
> Reason is mdev isn't physical device and doesn't support IOMMU_GET_HW_INFO.
>
> I thought ap/ccw are all mdev type and need a fix.
>
> This series depends on a patch from Joao which fixes the same for vfio-pci.
> See https://lists.gnu.org/archive/html/qemu-devel/2024-07/msg04612.html
>
> Not tested due to no ap/ccw environment. But build test pass.
>
> Thanks
> Zhenzhong
>
> Zhenzhong Duan (2):
> vfio/ap: Don't initialize HOST_IOMMU_DEVICE with mdev
> vfio/ccw: Don't initialize HOST_IOMMU_DEVICE with mdev
For the series
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Eric
>
> hw/vfio/ap.c | 3 +++
> hw/vfio/ccw.c | 3 +++
> 2 files changed, 6 insertions(+)
>
next prev parent reply other threads:[~2024-07-22 9:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 7:07 [PATCH 0/2] Don't initialize HOST_IOMMU_DEVICE with mdev Zhenzhong Duan
2024-07-22 7:07 ` [PATCH 1/2] vfio/ap: " Zhenzhong Duan
2024-07-22 9:18 ` Joao Martins
2024-07-22 15:46 ` Anthony Krowiak
2024-07-22 15:52 ` Joao Martins
2024-07-22 7:07 ` [PATCH 2/2] vfio/ccw: " Zhenzhong Duan
2024-07-22 9:18 ` Joao Martins
2024-07-22 14:57 ` Eric Farman
2024-07-22 15:09 ` Joao Martins
2024-07-22 15:36 ` Cédric Le Goater
2024-07-22 17:45 ` Eric Farman
2024-07-23 2:52 ` Duan, Zhenzhong
2024-07-22 9:31 ` Eric Auger [this message]
2024-07-22 10:02 ` [PATCH 0/2] " Cédric Le Goater
2024-07-22 13:50 ` Cédric Le Goater
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=536dcece-a249-4fe6-977d-d970795dfbe2@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chao.p.peng@intel.com \
--cc=clg@redhat.com \
--cc=joao.m.martins@oracle.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).