From: "Cédric Le Goater" <clg@redhat.com>
To: Eric Farman <farman@linux.ibm.com>, qemu-devel@nongnu.org
Cc: Zhenzhong Duan <zhenzhong.duan@intel.com>,
Eric Auger <eric.auger@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Nicholas Piggin <npiggin@gmail.com>,
Harsh Prateek Bora <harshpb@linux.ibm.com>
Subject: Re: [PATCH for-9.0 v2 00/10] vfio: Introduce a VFIOIOMMUClass
Date: Thu, 21 Dec 2023 08:59:40 +0100 [thread overview]
Message-ID: <79d175d1-1acd-4558-a30a-57c3376c9504@redhat.com> (raw)
In-Reply-To: <e215169f5504649cd3b8ec5ce66c988a8b5ba439.camel@linux.ibm.com>
On 12/20/23 21:35, Eric Farman wrote:
> On Tue, 2023-12-19 at 07:58 +0100, Cédric Le Goater wrote:
>> Hello,
>>
>> The VFIO object hierarchy has some constraints because each VFIO type
>> has a dual nature: a VFIO nature for passthrough support and a bus
>> nature (PCI, AP, CCW, Platform) for its initial presentation.
>
> The above caught my attention, so I kicked the tires on this series a
> little bit both with an iommufd-enabled host kernel and without, so I
> don't lose track of it over the holidays.
I don't plan to send a vfio PR in the current weeks. iommufd support is
upstream and still very warm and we should let it cool down during the
holidays.
> Tested-by: Eric Farman <farman@linux.ibm.com>
Thanks !
C.
prev parent reply other threads:[~2023-12-21 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 6:58 [PATCH for-9.0 v2 00/10] vfio: Introduce a VFIOIOMMUClass Cédric Le Goater
2023-12-19 6:58 ` [PATCH for-9.0 v2 01/10] vfio/spapr: Extend VFIOIOMMUOps with a release handler Cédric Le Goater
2023-12-19 6:58 ` [PATCH for-9.0 v2 02/10] vfio/container: Introduce vfio_legacy_setup() for further cleanups Cédric Le Goater
2023-12-19 6:58 ` [PATCH for-9.0 v2 03/10] vfio/container: Initialize VFIOIOMMUOps under vfio_init_container() Cédric Le Goater
2023-12-19 6:58 ` [PATCH for-9.0 v2 04/10] vfio/container: Introduce a VFIOIOMMU QOM interface Cédric Le Goater
2023-12-19 6:58 ` [PATCH for-9.0 v2 05/10] vfio/container: Introduce a VFIOIOMMU legacy " Cédric Le Goater
2023-12-19 6:58 ` [PATCH for-9.0 v2 06/10] vfio/container: Intoduce a new VFIOIOMMUClass::setup handler Cédric Le Goater
2023-12-19 6:58 ` [PATCH for-9.0 v2 07/10] vfio/spapr: Introduce a sPAPR VFIOIOMMU QOM interface Cédric Le Goater
2023-12-19 6:58 ` [PATCH for-9.0 v2 08/10] vfio/iommufd: Introduce a VFIOIOMMU iommufd " Cédric Le Goater
2023-12-19 6:58 ` [PATCH for-9.0 v2 09/10] vfio/spapr: Only compile sPAPR IOMMU support when needed Cédric Le Goater
2023-12-19 6:58 ` [PATCH for-9.0 v2 10/10] vfio/iommufd: Remove CONFIG_IOMMUFD usage Cédric Le Goater
2023-12-20 17:00 ` [PATCH for-9.0 v2 00/10] vfio: Introduce a VFIOIOMMUClass Cédric Le Goater
2023-12-20 20:35 ` Eric Farman
2023-12-21 7:59 ` Cédric Le Goater [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=79d175d1-1acd-4558-a30a-57c3376c9504@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=farman@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.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).