qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@redhat.com>
To: "Duan, Zhenzhong" <zhenzhong.duan@intel.com>,
	"Cédric Le Goater" <clg@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	"mst@redhat.com" <mst@redhat.com>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"peterx@redhat.com" <peterx@redhat.com>,
	"ddutile@redhat.com" <ddutile@redhat.com>,
	"jgg@nvidia.com" <jgg@nvidia.com>,
	"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
	"skolothumtho@nvidia.com" <skolothumtho@nvidia.com>,
	"joao.m.martins@oracle.com" <joao.m.martins@oracle.com>,
	"clement.mathieu--drif@eviden.com"
	<clement.mathieu--drif@eviden.com>,
	"Tian, Kevin" <kevin.tian@intel.com>,
	"Liu, Yi L" <yi.l.liu@intel.com>,
	"Peng, Chao P" <chao.p.peng@intel.com>
Subject: Re: [PATCH v7 05/23] hw/pci: Introduce pci_device_get_viommu_flags()
Date: Tue, 28 Oct 2025 16:19:27 +0100	[thread overview]
Message-ID: <dbdf9aaa-e238-4680-a66d-5759017c9e65@redhat.com> (raw)
In-Reply-To: <IA3PR11MB9136877A703966CA28C91D1792FDA@IA3PR11MB9136.namprd11.prod.outlook.com>



On 10/28/25 7:57 AM, Duan, Zhenzhong wrote:
>
>> -----Original Message-----
>> From: Cédric Le Goater <clg@redhat.com>
>> Subject: Re: [PATCH v7 05/23] hw/pci: Introduce
>> pci_device_get_viommu_flags()
>>
>> On 10/24/25 10:43, Zhenzhong Duan wrote:
>>> Introduce a new PCIIOMMUOps optional callback, get_viommu_flags()
>> which
>>> allows to retrieve flags exposed by a vIOMMU. The first planned vIOMMU
>>> device flag is VIOMMU_FLAG_WANT_NESTING_PARENT that advertises the
>>> support of HW nested stage translation scheme and wants other sub-system
>>> like VFIO's cooperation to create nesting parent HWPT.
>>>
>>> pci_device_get_viommu_flags() is a wrapper that can be called on a PCI
>>> device potentially protected by a vIOMMU.
>>>
>>> get_viommu_flags() is designed to return 64bit bitmap of purely vIOMMU
>>> flags which are only determined by user's configuration, no host
>>> capabilities involved. Reasons are:
>>>
>>> 1. host may has heterogeneous IOMMUs, each with different capabilities
>>> 2. this is migration friendly, return value is consistent between source
>>>     and target.
>>>
>>> Note that this op will be invoked at the attach_device() stage, at which
>>> point host IOMMU capabilities are not yet forwarded to the vIOMMU
>> through
>>> the set_iommu_device() callback that will be after the attach_device().
>>>
>>> See below sequence:
>>>
>>>    vfio_device_attach():
>>>        iommufd_cdev_attach():
>>>            pci_device_get_viommu_flags() for HW nesting cap
>>>            create a nesting parent HWPT
>>>            attach device to the HWPT
>>>            vfio_device_hiod_create_and_realize() creating hiod
>>>    ...
>>>    pci_device_set_iommu_device(hiod)
>>>
>>> Suggested-by: Yi Liu <yi.l.liu@intel.com>
>>> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
>>> Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
>>> Reviewed-by: Eric Auger <eric.auger@redhat.com>
>>> Reviewed-by: Yi Liu <yi.l.liu@intel.com>
>>> ---
>>>   MAINTAINERS          |  1 +
>>>   include/hw/iommu.h   | 25 +++++++++++++++++++++++++
>>
>> Hmm, why not under include/hw/pci/ ?
> I'm not sure if it's better to restrict iommu to pci subsystem.
> I have a vague memory there is iommu supporting non-PCI devices.

effectively on ARM we may need to support SMMU for platform devices too

Eric
>
>> Was this discussed ?
> No.
>
> Thanks
> Zhenzhong
>
>>
>> Reviewed-by: Cédric Le Goater <clg@redhat.com>
>>
>> Thanks,
>>
>> C.
>>
>>
>>
>>>   include/hw/pci/pci.h | 22 ++++++++++++++++++++++
>>>   hw/pci/pci.c         | 11 +++++++++++
>>>   4 files changed, 59 insertions(+)
>>>   create mode 100644 include/hw/iommu.h
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 36eef27b41..d94fbcbdfb 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -2338,6 +2338,7 @@ F: include/system/iommufd.h
>>>   F: backends/host_iommu_device.c
>>>   F: include/system/host_iommu_device.h
>>>   F: include/qemu/chardev_open.h
>>> +F: include/hw/iommu.h
>>>   F: util/chardev_open.c
>>>   F: docs/devel/vfio-iommufd.rst
>>>
>>> diff --git a/include/hw/iommu.h b/include/hw/iommu.h
>>> new file mode 100644
>>> index 0000000000..9b8bb94fc2
>>> --- /dev/null
>>> +++ b/include/hw/iommu.h
>>> @@ -0,0 +1,25 @@
>>> +/*
>>> + * General vIOMMU flags
>>> + *
>>> + * Copyright (C) 2025 Intel Corporation.
>>> + *
>>> + * SPDX-License-Identifier: GPL-2.0-or-later
>>> + */
>>> +
>>> +#ifndef HW_IOMMU_H
>>> +#define HW_IOMMU_H
>>> +
>>> +#include "qemu/bitops.h"
>>> +
>>> +/*
>>> + * Theoretical vIOMMU flags. Only determined by the vIOMMU device
>> properties and
>>> + * independent on the actual host IOMMU capabilities they may depend on.
>> Each
>>> + * flag can be an expectation or request to other sub-system or just a pure
>>> + * vIOMMU capability. vIOMMU can choose which flags to expose.
>>> + */
>>> +enum viommu_flags {
>>> +    /* vIOMMU needs nesting parent HWPT to create nested HWPT */
>>> +    VIOMMU_FLAG_WANT_NESTING_PARENT = BIT_ULL(0),
>>> +};
>>> +
>>> +#endif /* HW_IOMMU_H */
>>> diff --git a/include/hw/pci/pci.h b/include/hw/pci/pci.h
>>> index bde9dca8e2..cf99b5bb68 100644
>>> --- a/include/hw/pci/pci.h
>>> +++ b/include/hw/pci/pci.h
>>> @@ -462,6 +462,18 @@ typedef struct PCIIOMMUOps {
>>>        * @devfn: device and function number of the PCI device.
>>>        */
>>>       void (*unset_iommu_device)(PCIBus *bus, void *opaque, int devfn);
>>> +    /**
>>> +     * @get_viommu_flags: get vIOMMU flags
>>> +     *
>>> +     * Optional callback, if not implemented, then vIOMMU doesn't
>> support
>>> +     * exposing flags to other sub-system, e.g., VFIO.
>>> +     *
>>> +     * @opaque: the data passed to pci_setup_iommu().
>>> +     *
>>> +     * Returns: bitmap with each representing a vIOMMU flag defined in
>>> +     * enum viommu_flags.
>>> +     */
>>> +    uint64_t (*get_viommu_flags)(void *opaque);
>>>       /**
>>>        * @get_iotlb_info: get properties required to initialize a device
>> IOTLB.
>>>        *
>>> @@ -644,6 +656,16 @@ bool pci_device_set_iommu_device(PCIDevice
>> *dev, HostIOMMUDevice *hiod,
>>>                                    Error **errp);
>>>   void pci_device_unset_iommu_device(PCIDevice *dev);
>>>
>>> +/**
>>> + * pci_device_get_viommu_flags: get vIOMMU flags.
>>> + *
>>> + * Returns: bitmap with each representing a vIOMMU flag defined in
>>> + * enum viommu_flags. Or 0 if vIOMMU doesn't report any.
>>> + *
>>> + * @dev: PCI device pointer.
>>> + */
>>> +uint64_t pci_device_get_viommu_flags(PCIDevice *dev);
>>> +
>>>   /**
>>>    * pci_iommu_get_iotlb_info: get properties required to initialize a
>>>    * device IOTLB.
>>> diff --git a/hw/pci/pci.c b/hw/pci/pci.c
>>> index d0e81651aa..c9932c87e3 100644
>>> --- a/hw/pci/pci.c
>>> +++ b/hw/pci/pci.c
>>> @@ -3010,6 +3010,17 @@ void
>> pci_device_unset_iommu_device(PCIDevice *dev)
>>>       }
>>>   }
>>>
>>> +uint64_t pci_device_get_viommu_flags(PCIDevice *dev)
>>> +{
>>> +    PCIBus *iommu_bus;
>>> +
>>> +    pci_device_get_iommu_bus_devfn(dev, &iommu_bus, NULL, NULL);
>>> +    if (iommu_bus && iommu_bus->iommu_ops->get_viommu_flags) {
>>> +        return
>> iommu_bus->iommu_ops->get_viommu_flags(iommu_bus->iommu_opaque);
>>> +    }
>>> +    return 0;
>>> +}
>>> +
>>>   int pci_pri_request_page(PCIDevice *dev, uint32_t pasid, bool priv_req,
>>>                            bool exec_req, hwaddr addr, bool lpig,
>>>                            uint16_t prgi, bool is_read, bool is_write)



  reply	other threads:[~2025-10-28 15:20 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24  8:43 [PATCH v7 00/23] intel_iommu: Enable first stage translation for passthrough device Zhenzhong Duan
2025-10-24  8:43 ` [PATCH v7 01/23] intel_iommu: Rename vtd_ce_get_rid2pasid_entry to vtd_ce_get_pasid_entry Zhenzhong Duan
2025-10-24  8:43 ` [PATCH v7 02/23] intel_iommu: Delete RPS capability related supporting code Zhenzhong Duan
2025-10-31  7:50   ` Eric Auger
2025-10-31  9:49     ` Duan, Zhenzhong
2025-10-24  8:43 ` [PATCH v7 03/23] intel_iommu: Update terminology to match VTD spec Zhenzhong Duan
2025-10-24  8:43 ` [PATCH v7 04/23] hw/pci: Export pci_device_get_iommu_bus_devfn() and return bool Zhenzhong Duan
2025-10-24  8:43 ` [PATCH v7 05/23] hw/pci: Introduce pci_device_get_viommu_flags() Zhenzhong Duan
2025-10-24 17:18   ` Cédric Le Goater
2025-10-28  6:57     ` Duan, Zhenzhong
2025-10-28 15:19       ` Eric Auger [this message]
2025-10-24  8:43 ` [PATCH v7 06/23] intel_iommu: Implement get_viommu_flags() callback Zhenzhong Duan
2025-10-24  8:43 ` [PATCH v7 07/23] intel_iommu: Introduce a new structure VTDHostIOMMUDevice Zhenzhong Duan
2025-10-24  8:43 ` [PATCH v7 08/23] vfio/iommufd: Force creating nesting parent HWPT Zhenzhong Duan
2025-10-24 16:23   ` Cédric Le Goater
2025-10-28  6:00     ` Duan, Zhenzhong
2025-10-24  8:43 ` [PATCH v7 09/23] intel_iommu: Stick to system MR for IOMMUFD backed host device when x-flts=on Zhenzhong Duan
2025-10-31  8:09   ` Eric Auger
2025-10-31  9:52     ` Duan, Zhenzhong
2025-10-24  8:43 ` [PATCH v7 10/23] intel_iommu: Check for compatibility with IOMMUFD backed " Zhenzhong Duan
2025-10-24 17:29   ` Cédric Le Goater
2025-10-29  7:37     ` Duan, Zhenzhong
2025-10-24  8:43 ` [PATCH v7 11/23] intel_iommu: Fail passthrough device under PCI bridge if x-flts=on Zhenzhong Duan
2025-10-24  8:43 ` [PATCH v7 12/23] intel_iommu: Add some macros and inline functions Zhenzhong Duan
2025-10-24 16:39   ` Cédric Le Goater
2025-10-28  6:01     ` Duan, Zhenzhong
2025-11-02 11:15   ` Eric Auger
2025-11-03  3:44     ` Duan, Zhenzhong
2025-11-03  7:23       ` Eric Auger
2025-10-24  8:43 ` [PATCH v7 13/23] intel_iommu: Bind/unbind guest page table to host Zhenzhong Duan
2025-10-24 17:01   ` Cédric Le Goater
2025-11-03  9:25     ` Eric Auger
2025-10-24 17:33   ` Cédric Le Goater
2025-10-29  9:56     ` Duan, Zhenzhong
2025-11-03  9:37   ` Eric Auger
2025-10-24  8:43 ` [PATCH v7 14/23] intel_iommu: Propagate PASID-based iotlb invalidation " Zhenzhong Duan
2025-11-03 10:04   ` Eric Auger
2025-10-24  8:43 ` [PATCH v7 15/23] intel_iommu: Replay all pasid bindings when either SRTP or TE bit is changed Zhenzhong Duan
2025-10-24  8:43 ` [PATCH v7 16/23] intel_iommu: Replay pasid bindings after context cache invalidation Zhenzhong Duan
2025-11-03 10:45   ` Eric Auger
2025-10-24  8:43 ` [PATCH v7 17/23] iommufd: Introduce a helper function to extract vendor capabilities Zhenzhong Duan
2025-10-24 16:44   ` Cédric Le Goater
2025-10-28  9:43     ` Duan, Zhenzhong
2025-10-24 17:34   ` Cédric Le Goater
2025-10-28  9:28     ` Duan, Zhenzhong
2025-10-24  8:43 ` [PATCH v7 18/23] vfio: Add a new element bypass_ro in VFIOContainer Zhenzhong Duan
2025-10-24  8:43 ` [PATCH v7 19/23] Workaround for ERRATA_772415_SPR17 Zhenzhong Duan
2025-10-24 17:36   ` Cédric Le Goater
2025-10-24 17:38   ` Cédric Le Goater
2025-10-24  8:43 ` [PATCH v7 20/23] vfio: Bypass readonly region for dirty tracking Zhenzhong Duan
2025-10-24 16:32   ` Cédric Le Goater
2025-10-28  9:47     ` Duan, Zhenzhong
2025-10-24  8:43 ` [PATCH v7 21/23] intel_iommu: Add migration support with x-flts=on Zhenzhong Duan
2025-10-24  8:43 ` [PATCH v7 22/23] intel_iommu: Enable host device when x-flts=on in scalable mode Zhenzhong Duan
2025-10-24  8:43 ` [PATCH v7 23/23] docs/devel: Add IOMMUFD nesting documentation Zhenzhong Duan

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=dbdf9aaa-e238-4680-a66d-5759017c9e65@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=chao.p.peng@intel.com \
    --cc=clement.mathieu--drif@eviden.com \
    --cc=clg@redhat.com \
    --cc=ddutile@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=joao.m.martins@oracle.com \
    --cc=kevin.tian@intel.com \
    --cc=mst@redhat.com \
    --cc=nicolinc@nvidia.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=skolothumtho@nvidia.com \
    --cc=yi.l.liu@intel.com \
    --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).