From: "Cédric Le Goater" <clg@redhat.com>
To: "Duan, Zhenzhong" <zhenzhong.duan@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"mst@redhat.com" <mst@redhat.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"nicolinc@nvidia.com" <nicolinc@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>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v5 01/19] backends: Introduce HostIOMMUDevice abstract
Date: Mon, 27 May 2024 15:15:06 +0200 [thread overview]
Message-ID: <e4ce6f45-6232-4f62-a2d4-72a9e1e8c15c@redhat.com> (raw)
In-Reply-To: <SJ0PR11MB6744EEBF525D7057D396A09292E22@SJ0PR11MB6744.namprd11.prod.outlook.com>
On 5/13/24 12:28, Duan, Zhenzhong wrote:
> Hi Cédric,
>
>> -----Original Message-----
>> From: Cédric Le Goater <clg@redhat.com>
>> Subject: Re: [PATCH v5 01/19] backends: Introduce HostIOMMUDevice
>> abstract
>>
>> Hello Zhenzhong,
>>
>> On 5/8/24 11:03, Zhenzhong Duan wrote:
>>> Introduce HostIOMMUDevice as an abstraction of host IOMMU device.
>>>
>>> Introduce .realize() to initialize HostIOMMUDevice further after
>>> instance init.
>>>
>>> Introduce a macro CONFIG_HOST_IOMMU_DEVICE to define the usage
>>> for VFIO, and VDPA in the future.
>>
>> This looks like a way to work around some other problem, like
>> avoiding exposing Linux definitions on windows build.
>
> Yes, I have used this MACRO in patch19 to fix build failure on windows.
> Also need change HostIOMMUDeviceCaps::type to be uint32_t type.
Routine host_iommu_device_get_cap() could be open coded in vtd_check_hdev()
to avoid CONFIG_HOST_IOMMU_DEVICE.
Thanks,
C.
>
>>
>> Thanks,
>>
>> C.
>>
>>
>>
>>
>>>
>>> Suggested-by: Cédric Le Goater <clg@redhat.com>
>>> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
>>> ---
>>> MAINTAINERS | 2 ++
>>> include/sysemu/host_iommu_device.h | 51
>> ++++++++++++++++++++++++++++++
>>> backends/host_iommu_device.c | 30 ++++++++++++++++++
>>> backends/Kconfig | 5 +++
>>> backends/meson.build | 1 +
>>> 5 files changed, 89 insertions(+)
>>> create mode 100644 include/sysemu/host_iommu_device.h
>>> create mode 100644 backends/host_iommu_device.c
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 84391777db..5dab60bd04 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -2191,6 +2191,8 @@ M: Zhenzhong Duan
>> <zhenzhong.duan@intel.com>
>>> S: Supported
>>> F: backends/iommufd.c
>>> F: include/sysemu/iommufd.h
>>> +F: backends/host_iommu_device.c
>>> +F: include/sysemu/host_iommu_device.h
>>> F: include/qemu/chardev_open.h
>>> F: util/chardev_open.c
>>> F: docs/devel/vfio-iommufd.rst
>>> diff --git a/include/sysemu/host_iommu_device.h
>> b/include/sysemu/host_iommu_device.h
>>> new file mode 100644
>>> index 0000000000..2b58a94d62
>>> --- /dev/null
>>> +++ b/include/sysemu/host_iommu_device.h
>>> @@ -0,0 +1,51 @@
>>> +/*
>>> + * Host IOMMU device abstract declaration
>>> + *
>>> + * Copyright (C) 2024 Intel Corporation.
>>> + *
>>> + * Authors: Zhenzhong Duan <zhenzhong.duan@intel.com>
>>> + *
>>> + * This work is licensed under the terms of the GNU GPL, version 2. See
>>> + * the COPYING file in the top-level directory.
>>> + */
>>> +
>>> +#ifndef HOST_IOMMU_DEVICE_H
>>> +#define HOST_IOMMU_DEVICE_H
>>> +
>>> +#include "qom/object.h"
>>> +#include "qapi/error.h"
>>> +
>>> +#define TYPE_HOST_IOMMU_DEVICE "host-iommu-device"
>>> +OBJECT_DECLARE_TYPE(HostIOMMUDevice, HostIOMMUDeviceClass,
>> HOST_IOMMU_DEVICE)
>>> +
>>> +struct HostIOMMUDevice {
>>> + Object parent_obj;
>>> +};
>>> +
>>> +/**
>>> + * struct HostIOMMUDeviceClass - The base class for all host IOMMU
>> devices.
>>> + *
>>> + * Different type of host devices (e.g., VFIO or VDPA device) or devices
>>> + * with different backend (e.g., VFIO legacy container or IOMMUFD
>> backend)
>>> + * can have different sub-classes.
>>> + */
>>> +struct HostIOMMUDeviceClass {
>>> + ObjectClass parent_class;
>>> +
>>> + /**
>>> + * @realize: initialize host IOMMU device instance further.
>>> + *
>>> + * Mandatory callback.
>>> + *
>>> + * @hiod: pointer to a host IOMMU device instance.
>>> + *
>>> + * @opaque: pointer to agent device of this host IOMMU device,
>>> + * i.e., for VFIO, pointer to VFIODevice
>>> + *
>>> + * @errp: pass an Error out when realize fails.
>>> + *
>>> + * Returns: true on success, false on failure.
>>> + */
>>> + bool (*realize)(HostIOMMUDevice *hiod, void *opaque, Error **errp);
>>> +};
>>> +#endif
>>> diff --git a/backends/host_iommu_device.c
>> b/backends/host_iommu_device.c
>>> new file mode 100644
>>> index 0000000000..41f2fdce20
>>> --- /dev/null
>>> +++ b/backends/host_iommu_device.c
>>> @@ -0,0 +1,30 @@
>>> +/*
>>> + * Host IOMMU device abstract
>>> + *
>>> + * Copyright (C) 2024 Intel Corporation.
>>> + *
>>> + * Authors: Zhenzhong Duan <zhenzhong.duan@intel.com>
>>> + *
>>> + * This work is licensed under the terms of the GNU GPL, version 2. See
>>> + * the COPYING file in the top-level directory.
>>> + */
>>> +
>>> +#include "qemu/osdep.h"
>>> +#include "sysemu/host_iommu_device.h"
>>> +
>>> +OBJECT_DEFINE_ABSTRACT_TYPE(HostIOMMUDevice,
>>> + host_iommu_device,
>>> + HOST_IOMMU_DEVICE,
>>> + OBJECT)
>>> +
>>> +static void host_iommu_device_class_init(ObjectClass *oc, void *data)
>>> +{
>>> +}
>>> +
>>> +static void host_iommu_device_init(Object *obj)
>>> +{
>>> +}
>>> +
>>> +static void host_iommu_device_finalize(Object *obj)
>>> +{
>>> +}
>>> diff --git a/backends/Kconfig b/backends/Kconfig
>>> index 2cb23f62fa..34ab29e994 100644
>>> --- a/backends/Kconfig
>>> +++ b/backends/Kconfig
>>> @@ -3,3 +3,8 @@ source tpm/Kconfig
>>> config IOMMUFD
>>> bool
>>> depends on VFIO
>>> +
>>> +config HOST_IOMMU_DEVICE
>>> + bool
>>> + default y
>>> + depends on VFIO
>>> diff --git a/backends/meson.build b/backends/meson.build
>>> index 8b2b111497..2e975d641e 100644
>>> --- a/backends/meson.build
>>> +++ b/backends/meson.build
>>> @@ -25,6 +25,7 @@ if have_vhost_user
>>> endif
>>> system_ss.add(when: 'CONFIG_VIRTIO_CRYPTO', if_true: files('cryptodev-
>> vhost.c'))
>>> system_ss.add(when: 'CONFIG_IOMMUFD', if_true: files('iommufd.c'))
>>> +system_ss.add(when: 'CONFIG_HOST_IOMMU_DEVICE', if_true:
>> files('host_iommu_device.c'))
>>
>> Euh. Why is that ?
>
> Tried to reduce qemu binary size a bit.
> When CONFIG_VFIO=n such as on windows, CONFIG_HOST_IOMMU_DEVICE=n.
> There is no user of host_iommu_device.c, so no need to build it.
> But this way need to add '#ifdef CONFIG_HOST_IOMMU_DEVICE' in vtd_check_hdev() in intel_iommu.c.
>
> The other way is to drop this build configuration, then there is no need to add '#ifdef CONFIG_HOST_IOMMU_DEVICE' in vtd_check_hdev() in intel_iommu.c, because
> host_iommu_device.c is always built.
>
> This series works in 1st way, I can change to 2nd way if you prefer.
>
> Thanks
> Zhenzhong
>
>
>
next prev parent reply other threads:[~2024-05-27 13:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 9:03 [PATCH v5 00/19] Add a host IOMMU device abstraction to check with vIOMMU Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 01/19] backends: Introduce HostIOMMUDevice abstract Zhenzhong Duan
2024-05-13 9:29 ` Cédric Le Goater
2024-05-13 10:28 ` Duan, Zhenzhong
2024-05-27 13:15 ` Cédric Le Goater [this message]
2024-05-08 9:03 ` [PATCH v5 02/19] vfio/container: Introduce TYPE_HOST_IOMMU_DEVICE_LEGACY_VFIO device Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 03/19] backends/iommufd: Introduce abstract TYPE_HOST_IOMMU_DEVICE_IOMMUFD device Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 04/19] vfio/iommufd: Introduce TYPE_HOST_IOMMU_DEVICE_IOMMUFD_VFIO device Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 05/19] backends/host_iommu_device: Introduce HostIOMMUDeviceCaps Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 06/19] range: Introduce range_get_last_bit() Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 07/19] vfio/container: Implement HostIOMMUDeviceClass::realize() handler Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 08/19] backends/iommufd: Introduce helper function iommufd_backend_get_device_info() Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 09/19] vfio/iommufd: Implement HostIOMMUDeviceClass::realize() handler Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 10/19] vfio/container: Implement HostIOMMUDeviceClass::get_cap() handler Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 11/19] backends/iommufd: " Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 12/19] vfio: Introduce VFIOIOMMUClass::hiod_typename attribute Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 13/19] vfio: Create host IOMMU device instance Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 14/19] hw/pci: Introduce helper function pci_device_get_iommu_bus_devfn() Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 15/19] hw/pci: Introduce pci_device_[set|unset]_iommu_device() Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 16/19] vfio/pci: Pass HostIOMMUDevice to vIOMMU Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 17/19] intel_iommu: Extract out vtd_cap_init() to initialize cap/ecap Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 18/19] intel_iommu: Implement [set|unset]_iommu_device() callbacks Zhenzhong Duan
2024-05-08 9:03 ` [PATCH v5 19/19] intel_iommu: Check compatibility with host IOMMU capabilities Zhenzhong Duan
2024-05-27 13:18 ` Cédric Le Goater
2024-05-28 3:00 ` 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=e4ce6f45-6232-4f62-a2d4-72a9e1e8c15c@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chao.p.peng@intel.com \
--cc=clement.mathieu--drif@eviden.com \
--cc=eric.auger@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=pbonzini@redhat.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).