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, mst@redhat.com,
peterx@redhat.com, jasowang@redhat.com, jgg@nvidia.com,
nicolinc@nvidia.com, joao.m.martins@oracle.com,
clement.mathieu--drif@eviden.com, kevin.tian@intel.com,
yi.l.liu@intel.com, chao.p.peng@intel.com
Subject: Re: [PATCH v6 03/19] backends/iommufd: Introduce abstract TYPE_HOST_IOMMU_DEVICE_IOMMUFD device
Date: Mon, 3 Jun 2024 14:50:04 +0200 [thread overview]
Message-ID: <f64ffbd9-fb34-474d-be4a-66c4c9ee223b@redhat.com> (raw)
In-Reply-To: <20240603061023.269738-4-zhenzhong.duan@intel.com>
Hi Zhenzhong,
On 6/3/24 08:10, Zhenzhong Duan wrote:
> TYPE_HOST_IOMMU_DEVICE_IOMMUFD represents a host IOMMU device under
> iommufd backend.
>
> It will have its own .get_cap() implementation.
>
> Opportunistically, add missed header to include/sysemu/iommufd.h.
I would explain why it is abstract, ie. because it is going to be
derived into VFIO or VDPA type'd device.
Besides I think I would simply squash patches 3 and 4
Thanks
Eric
>
> Suggested-by: Cédric Le Goater <clg@redhat.com>
> Signed-off-by: Yi Liu <yi.l.liu@intel.com>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> ---
> include/sysemu/iommufd.h | 16 ++++++++++++++++
> backends/iommufd.c | 35 ++++++++++++++++++-----------------
> 2 files changed, 34 insertions(+), 17 deletions(-)
>
> diff --git a/include/sysemu/iommufd.h b/include/sysemu/iommufd.h
> index 293bfbe967..f6e6d6e1f9 100644
> --- a/include/sysemu/iommufd.h
> +++ b/include/sysemu/iommufd.h
> @@ -1,9 +1,23 @@
> +/*
> + * iommufd container backend declaration
> + *
> + * Copyright (C) 2024 Intel Corporation.
> + * Copyright Red Hat, Inc. 2024
> + *
> + * Authors: Yi Liu <yi.l.liu@intel.com>
> + * Eric Auger <eric.auger@redhat.com>
> + * Zhenzhong Duan <zhenzhong.duan@intel.com>
> + *
> + * SPDX-License-Identifier: GPL-2.0-or-later
> + */
> +
> #ifndef SYSEMU_IOMMUFD_H
> #define SYSEMU_IOMMUFD_H
>
> #include "qom/object.h"
> #include "exec/hwaddr.h"
> #include "exec/cpu-common.h"
> +#include "sysemu/host_iommu_device.h"
>
> #define TYPE_IOMMUFD_BACKEND "iommufd"
> OBJECT_DECLARE_TYPE(IOMMUFDBackend, IOMMUFDBackendClass, IOMMUFD_BACKEND)
> @@ -33,4 +47,6 @@ int iommufd_backend_map_dma(IOMMUFDBackend *be, uint32_t ioas_id, hwaddr iova,
> ram_addr_t size, void *vaddr, bool readonly);
> int iommufd_backend_unmap_dma(IOMMUFDBackend *be, uint32_t ioas_id,
> hwaddr iova, ram_addr_t size);
> +
> +#define TYPE_HOST_IOMMU_DEVICE_IOMMUFD TYPE_HOST_IOMMU_DEVICE "-iommufd"
> #endif
> diff --git a/backends/iommufd.c b/backends/iommufd.c
> index c506afbdac..012f18d8d8 100644
> --- a/backends/iommufd.c
> +++ b/backends/iommufd.c
> @@ -208,23 +208,24 @@ int iommufd_backend_unmap_dma(IOMMUFDBackend *be, uint32_t ioas_id,
> return ret;
> }
>
> -static const TypeInfo iommufd_backend_info = {
> - .name = TYPE_IOMMUFD_BACKEND,
> - .parent = TYPE_OBJECT,
> - .instance_size = sizeof(IOMMUFDBackend),
> - .instance_init = iommufd_backend_init,
> - .instance_finalize = iommufd_backend_finalize,
> - .class_size = sizeof(IOMMUFDBackendClass),
> - .class_init = iommufd_backend_class_init,
> - .interfaces = (InterfaceInfo[]) {
> - { TYPE_USER_CREATABLE },
> - { }
> +static const TypeInfo types[] = {
> + {
> + .name = TYPE_IOMMUFD_BACKEND,
> + .parent = TYPE_OBJECT,
> + .instance_size = sizeof(IOMMUFDBackend),
> + .instance_init = iommufd_backend_init,
> + .instance_finalize = iommufd_backend_finalize,
> + .class_size = sizeof(IOMMUFDBackendClass),
> + .class_init = iommufd_backend_class_init,
> + .interfaces = (InterfaceInfo[]) {
> + { TYPE_USER_CREATABLE },
> + { }
> + }
> + }, {
> + .name = TYPE_HOST_IOMMU_DEVICE_IOMMUFD,
> + .parent = TYPE_HOST_IOMMU_DEVICE,
> + .abstract = true,
> }
> };
>
> -static void register_types(void)
> -{
> - type_register_static(&iommufd_backend_info);
> -}
> -
> -type_init(register_types);
> +DEFINE_TYPES(types)
next prev parent reply other threads:[~2024-06-03 12:50 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 6:10 [PATCH v6 00/19] Add a host IOMMU device abstraction to check with vIOMMU Zhenzhong Duan
2024-06-03 6:10 ` [PATCH v6 01/19] backends: Introduce HostIOMMUDevice abstract Zhenzhong Duan
2024-06-03 12:16 ` Cédric Le Goater
2024-06-04 3:10 ` Duan, Zhenzhong
2024-06-03 12:46 ` Eric Auger
2024-06-04 3:41 ` Duan, Zhenzhong
2024-06-03 6:10 ` [PATCH v6 02/19] vfio/container: Introduce TYPE_HOST_IOMMU_DEVICE_LEGACY_VFIO device Zhenzhong Duan
2024-06-03 6:10 ` [PATCH v6 03/19] backends/iommufd: Introduce abstract TYPE_HOST_IOMMU_DEVICE_IOMMUFD device Zhenzhong Duan
2024-06-03 12:50 ` Eric Auger [this message]
2024-06-04 3:43 ` Duan, Zhenzhong
2024-06-03 6:10 ` [PATCH v6 04/19] vfio/iommufd: Introduce TYPE_HOST_IOMMU_DEVICE_IOMMUFD_VFIO device Zhenzhong Duan
2024-06-03 6:10 ` [PATCH v6 05/19] backends/host_iommu_device: Introduce HostIOMMUDeviceCaps Zhenzhong Duan
2024-06-03 12:40 ` Cédric Le Goater
2024-06-03 12:51 ` Eric Auger
2024-06-03 6:10 ` [PATCH v6 06/19] range: Introduce range_get_last_bit() Zhenzhong Duan
2024-06-03 12:57 ` Eric Auger
2024-06-03 6:10 ` [PATCH v6 07/19] vfio/container: Implement HostIOMMUDeviceClass::realize() handler Zhenzhong Duan
2024-06-03 11:23 ` Eric Auger
2024-06-04 2:45 ` Duan, Zhenzhong
2024-06-04 7:45 ` Eric Auger
2024-06-04 7:59 ` Duan, Zhenzhong
2024-06-03 6:10 ` [PATCH v6 08/19] backends/iommufd: Introduce helper function iommufd_backend_get_device_info() Zhenzhong Duan
2024-06-03 6:10 ` [PATCH v6 09/19] vfio/iommufd: Implement HostIOMMUDeviceClass::realize() handler Zhenzhong Duan
2024-06-03 11:30 ` Eric Auger
2024-06-04 2:58 ` Duan, Zhenzhong
2024-06-04 7:31 ` Eric Auger
2024-06-04 7:51 ` Duan, Zhenzhong
2024-06-04 8:08 ` Eric Auger
2024-06-04 8:39 ` Duan, Zhenzhong
2024-06-06 9:26 ` Eric Auger
2024-06-06 9:32 ` Eric Auger
2024-06-06 10:19 ` Duan, Zhenzhong
2024-06-03 6:10 ` [PATCH v6 10/19] vfio/container: Implement HostIOMMUDeviceClass::get_cap() handler Zhenzhong Duan
2024-06-03 6:10 ` [PATCH v6 11/19] backends/iommufd: " Zhenzhong Duan
2024-06-03 11:32 ` Eric Auger
2024-06-03 12:35 ` Cédric Le Goater
2024-06-04 3:23 ` Duan, Zhenzhong
2024-06-04 8:10 ` Eric Auger
2024-06-04 8:46 ` Duan, Zhenzhong
2024-06-04 9:37 ` Eric Auger
2024-06-03 6:10 ` [PATCH v6 12/19] vfio: Introduce VFIOIOMMUClass::hiod_typename attribute Zhenzhong Duan
2024-06-03 6:10 ` [PATCH v6 13/19] vfio: Create host IOMMU device instance Zhenzhong Duan
2024-06-03 12:59 ` Eric Auger
2024-06-04 3:47 ` Duan, Zhenzhong
2024-06-03 6:10 ` [PATCH v6 14/19] hw/pci: Introduce helper function pci_device_get_iommu_bus_devfn() Zhenzhong Duan
2024-06-03 13:40 ` Eric Auger
2024-06-03 6:10 ` [PATCH v6 15/19] hw/pci: Introduce pci_device_[set|unset]_iommu_device() Zhenzhong Duan
2024-06-03 13:54 ` Eric Auger
2024-06-03 6:10 ` [PATCH v6 16/19] vfio/pci: Pass HostIOMMUDevice to vIOMMU Zhenzhong Duan
2024-06-03 13:54 ` Eric Auger
2024-06-03 6:10 ` [PATCH v6 17/19] intel_iommu: Extract out vtd_cap_init() to initialize cap/ecap Zhenzhong Duan
2024-06-03 6:10 ` [PATCH v6 18/19] intel_iommu: Implement [set|unset]_iommu_device() callbacks Zhenzhong Duan
2024-06-03 10:12 ` CLEMENT MATHIEU--DRIF
2024-06-03 11:02 ` Duan, Zhenzhong
2024-06-03 12:56 ` Cédric Le Goater
2024-06-04 3:46 ` Duan, Zhenzhong
2024-06-03 14:13 ` Eric Auger
2024-06-04 5:40 ` Duan, Zhenzhong
2024-06-04 8:14 ` Eric Auger
2024-06-04 8:48 ` Duan, Zhenzhong
2024-06-04 9:38 ` Eric Auger
2024-06-03 14:47 ` Eric Auger
2024-06-04 5:46 ` Duan, Zhenzhong
2024-06-04 8:17 ` Eric Auger
2024-06-06 4:04 ` Duan, Zhenzhong
2024-06-03 6:10 ` [PATCH v6 19/19] intel_iommu: Check compatibility with host IOMMU capabilities Zhenzhong Duan
2024-06-03 14:23 ` Eric Auger
2024-06-04 5:46 ` Duan, Zhenzhong
2024-06-03 12:43 ` [PATCH v6 00/19] Add a host IOMMU device abstraction to check with vIOMMU Eric Auger
2024-06-04 3:32 ` Duan, Zhenzhong
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=f64ffbd9-fb34-474d-be4a-66c4c9ee223b@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=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=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).