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>,
"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>
Subject: Re: [PATCH v6 11/19] backends/iommufd: Implement HostIOMMUDeviceClass::get_cap() handler
Date: Tue, 4 Jun 2024 11:37:27 +0200 [thread overview]
Message-ID: <c21bd141-96fe-475a-a645-8dc392ff2450@redhat.com> (raw)
In-Reply-To: <SJ0PR11MB67444BA9CD463A744C9A616292F82@SJ0PR11MB6744.namprd11.prod.outlook.com>
On 6/4/24 10:46, Duan, Zhenzhong wrote:
>
>> -----Original Message-----
>> From: Eric Auger <eric.auger@redhat.com>
>> Subject: Re: [PATCH v6 11/19] backends/iommufd: Implement
>> HostIOMMUDeviceClass::get_cap() handler
>>
>>
>>
>> On 6/4/24 05:23, Duan, Zhenzhong wrote:
>>> Hi Cédric, Eric,
>>>
>>>> -----Original Message-----
>>>> From: Cédric Le Goater <clg@redhat.com>
>>>> Subject: Re: [PATCH v6 11/19] backends/iommufd: Implement
>>>> HostIOMMUDeviceClass::get_cap() handler
>>>>
>>>> On 6/3/24 13:32, Eric Auger wrote:
>>>>> On 6/3/24 08:10, Zhenzhong Duan wrote:
>>>>>> Suggested-by: Cédric Le Goater <clg@redhat.com>
>>>>>> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
>>>>>> ---
>>>>>> backends/iommufd.c | 23 +++++++++++++++++++++++
>>>>>> 1 file changed, 23 insertions(+)
>>>>>>
>>>>>> diff --git a/backends/iommufd.c b/backends/iommufd.c
>>>>>> index c7e969d6f7..f2f7a762a0 100644
>>>>>> --- a/backends/iommufd.c
>>>>>> +++ b/backends/iommufd.c
>>>>>> @@ -230,6 +230,28 @@ bool
>>>> iommufd_backend_get_device_info(IOMMUFDBackend *be, uint32_t
>> devid,
>>>>>> return true;
>>>>>> }
>>>>>>
>>>>>> +static int hiod_iommufd_get_cap(HostIOMMUDevice *hiod, int cap,
>>>> Error **errp)
>>>>>> +{
>>>>>> + HostIOMMUDeviceCaps *caps = &hiod->caps;
>>>>>> +
>>>>>> + switch (cap) {
>>>>>> + case HOST_IOMMU_DEVICE_CAP_IOMMU_TYPE:
>>>>>> + return caps->type;
>>>>>> + case HOST_IOMMU_DEVICE_CAP_AW_BITS:
>>>>>> + return caps->aw_bits;
>>>>>> + default:
>>>>>> + error_setg(errp, "Not support get cap %x", cap);
>>>>> can't you add details about the faulting HostIOMMUDevice by tracing
>> the
>>>>> devid for instance?
>>>> yes.
>>> devid isn't added to make this series simpler.
>>> It's added in nesting series,
>> https://github.com/yiliu1765/qemu/commit/5333b1a0ae03b3c5119b46a1
>> af786d199f103889
>>> Do you want to add devid in this series for tracing purpose or adding trace
>> in nesting series is fine for you?
>>
>> what would be nice is to get a common way to identify a HostIOMMUDevice,
>> can't we use the name of the VFIO/VDPA device? devid does not exist on
>> legacy container. At least a kind of wrapper may be relevant to extract
>> the name.
> Getting name directly is not easy, we can save a copy in .realize(), like below:
sounds good + dealloc
Eric
>
> --- a/include/sysemu/host_iommu_device.h
> +++ b/include/sysemu/host_iommu_device.h
> @@ -33,6 +33,7 @@ OBJECT_DECLARE_TYPE(HostIOMMUDevice, HostIOMMUDeviceClass, HOST_IOMMU_DEVICE)
> struct HostIOMMUDevice {
> Object parent_obj;
>
> + char *name;
> HostIOMMUDeviceCaps caps;
> };
>
> diff --git a/backends/iommufd.c b/backends/iommufd.c
> index f2f7a762a0..84fefbc9ee 100644
> --- a/backends/iommufd.c
> +++ b/backends/iommufd.c
> @@ -240,7 +240,7 @@ static int hiod_iommufd_get_cap(HostIOMMUDevice *hiod, int cap, Error **errp)
> case HOST_IOMMU_DEVICE_CAP_AW_BITS:
> return caps->aw_bits;
> default:
> - error_setg(errp, "Not support get cap %x", cap);
> + error_setg(errp, "%s: unsupported capability %x", hiod->name, cap);
> return -EINVAL;
> }
> }
> diff --git a/hw/vfio/container.c b/hw/vfio/container.c
> index a830426647..e78538efec 100644
> --- a/hw/vfio/container.c
> +++ b/hw/vfio/container.c
> @@ -1152,6 +1152,7 @@ static bool hiod_legacy_vfio_realize(HostIOMMUDevice *hiod, void *opaque,
> } else {
> hiod->caps.aw_bits = 0xff;
> }
> + hiod->name = g_strdup(vdev->name);
>
> return true;
> }
> @@ -1165,7 +1166,7 @@ static int hiod_legacy_vfio_get_cap(HostIOMMUDevice *hiod, int cap,
> case HOST_IOMMU_DEVICE_CAP_AW_BITS:
> return caps->aw_bits;
> default:
> - error_setg(errp, "Not support get cap %x", cap);
> + error_setg(errp, "%s: unsupported capability %x", hiod->name, cap);
> return -EINVAL;
> }
> }
> diff --git a/hw/vfio/iommufd.c b/hw/vfio/iommufd.c
> index 8fd8d52bc2..2df3aed47f 100644
> --- a/hw/vfio/iommufd.c
> +++ b/hw/vfio/iommufd.c
> @@ -637,6 +637,7 @@ static bool hiod_iommufd_vfio_realize(HostIOMMUDevice *hiod, void *opaque,
> return false;
> }
>
> + hiod->name = g_strdup(vdev->name);
> caps->type = type;
next prev parent reply other threads:[~2024-06-04 9:38 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
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 [this message]
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=c21bd141-96fe-475a-a645-8dc392ff2450@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).