qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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, peterx@redhat.com,
	jasowang@redhat.com, mst@redhat.com, jgg@nvidia.com,
	nicolinc@nvidia.com, joao.m.martins@oracle.com,
	kevin.tian@intel.com, yi.l.liu@intel.com, yi.y.sun@intel.com,
	chao.p.peng@intel.com
Subject: Re: [PATCH v1 01/11] Introduce a common abstract struct HostIOMMUDevice
Date: Mon, 18 Mar 2024 15:23:54 +0100	[thread overview]
Message-ID: <2d9b6b71-6913-4169-9759-0b25ae9eddbc@redhat.com> (raw)
In-Reply-To: <20240228035900.1085727-2-zhenzhong.duan@intel.com>

Hi Zhenzhong,
On 2/28/24 04:58, Zhenzhong Duan wrote:
> HostIOMMUDevice will be inherited by two sub classes,
> legacy and iommufd currently.
As this patch introduces the object, you describe what the object is
meant for and used for. Maybe reuse text from the cover letter

Thanks

Eric
>
> Introduce a helper function host_iommu_base_device_init to initialize it.
>
> Suggested-by: Eric Auger <eric.auger@redhat.com>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> ---
>  include/sysemu/host_iommu_device.h | 22 ++++++++++++++++++++++
>  1 file changed, 22 insertions(+)
>  create mode 100644 include/sysemu/host_iommu_device.h
>
> diff --git a/include/sysemu/host_iommu_device.h b/include/sysemu/host_iommu_device.h
> new file mode 100644
> index 0000000000..fe80ab25fb
> --- /dev/null
> +++ b/include/sysemu/host_iommu_device.h
> @@ -0,0 +1,22 @@
> +#ifndef HOST_IOMMU_DEVICE_H
> +#define HOST_IOMMU_DEVICE_H
> +
> +typedef enum HostIOMMUDevice_Type {
> +    HID_LEGACY,
> +    HID_IOMMUFD,
> +    HID_MAX,
> +} HostIOMMUDevice_Type;
> +
> +typedef struct HostIOMMUDevice {
> +    HostIOMMUDevice_Type type;
> +    size_t size;
> +} HostIOMMUDevice;
> +
> +static inline void host_iommu_base_device_init(HostIOMMUDevice *dev,
> +                                               HostIOMMUDevice_Type type,
> +                                               size_t size)
> +{
> +    dev->type = type;
> +    dev->size = size;
> +}
> +#endif



  reply	other threads:[~2024-03-18 14:25 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28  3:58 [PATCH v1 00/11] Add a host IOMMU device abstraction Zhenzhong Duan
2024-02-28  3:58 ` [PATCH v1 01/11] Introduce a common abstract struct HostIOMMUDevice Zhenzhong Duan
2024-03-18 14:23   ` Eric Auger [this message]
2024-03-19  3:48     ` Duan, Zhenzhong
2024-03-19  8:16   ` Cédric Le Goater
2024-03-19 11:58     ` Duan, Zhenzhong
2024-03-27 10:25       ` Cédric Le Goater
2024-03-28  3:06         ` Duan, Zhenzhong
2024-03-29 15:30           ` Cédric Le Goater
2024-04-01  3:59             ` Duan, Zhenzhong
2024-02-28  3:58 ` [PATCH v1 02/11] backends/iommufd: Introduce IOMMUFDDevice Zhenzhong Duan
2024-02-28  3:58 ` [PATCH v1 03/11] vfio: Introduce IOMMULegacyDevice Zhenzhong Duan
2024-02-28  3:58 ` [PATCH v1 04/11] vfio: Add HostIOMMUDevice handle into VFIODevice Zhenzhong Duan
2024-03-18 13:49   ` Eric Auger
2024-03-19  3:05     ` Duan, Zhenzhong
2024-02-28  3:58 ` [PATCH v1 05/11] vfio: Introduce host_iommu_device_create callback Zhenzhong Duan
2024-03-18 13:52   ` Eric Auger
2024-03-18 14:23     ` Eric Auger
2024-03-19  3:14       ` Duan, Zhenzhong
2024-03-19  3:12     ` Duan, Zhenzhong
2024-03-18 14:32   ` Eric Auger
2024-03-19  5:44     ` Duan, Zhenzhong
2024-03-19  7:16       ` Eric Auger
2024-02-28  3:58 ` [PATCH v1 06/11] vfio/container: Implement host_iommu_device_create callback in legacy mode Zhenzhong Duan
2024-02-28  3:58 ` [PATCH v1 07/11] vfio/iommufd: Implement host_iommu_device_create callback in iommufd mode Zhenzhong Duan
2024-02-28  3:58 ` [PATCH v1 08/11] vfio/pci: Allocate and initialize HostIOMMUDevice after attachment Zhenzhong Duan
2024-03-18 14:27   ` Eric Auger
2024-03-19  3:46     ` Duan, Zhenzhong
2024-03-19  7:18       ` Eric Auger
2024-02-28  3:58 ` [PATCH v1 09/11] hw/pci: Introduce pci_device_set/unset_iommu_device() Zhenzhong Duan
2024-03-12 16:55   ` Michael S. Tsirkin
2024-03-12 17:10     ` Michael S. Tsirkin
2024-03-18 14:49   ` Eric Auger
2024-03-19  6:16     ` Duan, Zhenzhong
2024-02-28  3:58 ` [PATCH v1 10/11] vfio: Pass HostIOMMUDevice to vIOMMU Zhenzhong Duan
2024-02-28  3:59 ` [PATCH v1 11/11] backends/iommufd: Introduce helper function iommufd_device_get_info() Zhenzhong Duan
2024-03-18 14:54   ` Eric Auger
2024-03-18 15:09     ` Joao Martins
2024-03-18 15:11       ` Eric Auger
2024-03-19  6:25         ` Duan, Zhenzhong
2024-03-18 14:57 ` [PATCH v1 00/11] Add a host IOMMU device abstraction Eric Auger
2024-03-19  6:26   ` 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=2d9b6b71-6913-4169-9759-0b25ae9eddbc@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=chao.p.peng@intel.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=yi.y.sun@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).