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, 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 07/19] vfio/container: Implement HostIOMMUDeviceClass::realize() handler
Date: Mon, 3 Jun 2024 13:23:18 +0200	[thread overview]
Message-ID: <1a188365-7101-472d-adfb-89a74dab055b@redhat.com> (raw)
In-Reply-To: <20240603061023.269738-8-zhenzhong.duan@intel.com>

Hi Zhenzhong,

On 6/3/24 08:10, Zhenzhong Duan wrote:
> Utilize range_get_last_bit() to get host IOMMU address width and
> package it in HostIOMMUDeviceCaps for query with .get_cap().
>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> ---
>  hw/vfio/container.c | 26 ++++++++++++++++++++++++++
>  1 file changed, 26 insertions(+)
>
> diff --git a/hw/vfio/container.c b/hw/vfio/container.c
> index c4fca2dfca..48800fe92f 100644
> --- a/hw/vfio/container.c
> +++ b/hw/vfio/container.c
> @@ -1136,6 +1136,31 @@ static void vfio_iommu_legacy_class_init(ObjectClass *klass, void *data)
>      vioc->pci_hot_reset = vfio_legacy_pci_hot_reset;
>  };
>  
> +static bool hiod_legacy_vfio_realize(HostIOMMUDevice *hiod, void *opaque,
> +                                     Error **errp)
> +{
> +    VFIODevice *vdev = opaque;
> +    /* iova_ranges is a sorted list */
> +    GList *l = g_list_last(vdev->bcontainer->iova_ranges);
> +
> +    /* Only support query HOST_IOMMU_DEVICE_CAP_AW_BITS with legacy backend */
I don't get the comment as HOST_IOMMU_DEVICE_CAP_AW_BITS support seems
to be introduced in [PATCH v6 11/19] backends/iommufd: Implement
HostIOMMUDeviceClass::get_cap() handler
> +    if (l) {
> +        Range *range = l->data;
> +        hiod->caps.aw_bits = range_get_last_bit(range) + 1;
> +    } else {
> +        hiod->caps.aw_bits = 0xff;
why this value?
> +    }
> +
> +    return true;
> +}
> +
> +static void hiod_legacy_vfio_class_init(ObjectClass *oc, void *data)
> +{
> +    HostIOMMUDeviceClass *hioc = HOST_IOMMU_DEVICE_CLASS(oc);
> +
> +    hioc->realize = hiod_legacy_vfio_realize;
> +};
> +
>  static const TypeInfo types[] = {
>      {
>          .name = TYPE_VFIO_IOMMU_LEGACY,
> @@ -1144,6 +1169,7 @@ static const TypeInfo types[] = {
>      }, {
>          .name = TYPE_HOST_IOMMU_DEVICE_LEGACY_VFIO,
>          .parent = TYPE_HOST_IOMMU_DEVICE,
> +        .class_init = hiod_legacy_vfio_class_init,
>      }
>  };
>  

Thanks

Eric



  reply	other threads:[~2024-06-03 11:23 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 [this message]
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=1a188365-7101-472d-adfb-89a74dab055b@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).