From: Nicolin Chen via <qemu-devel@nongnu.org>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>
Cc: <qemu-devel@nongnu.org>, <alex.williamson@redhat.com>,
<clg@redhat.com>, <eric.auger@redhat.com>, <mst@redhat.com>,
<jasowang@redhat.com>, <peterx@redhat.com>, <ddutile@redhat.com>,
<jgg@nvidia.com>, <shameerali.kolothum.thodi@huawei.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 v2 3/4] vfio/iommufd: Implement [at|de]tach_hwpt handlers
Date: Fri, 30 May 2025 13:31:29 -0700 [thread overview]
Message-ID: <aDoVoaWGIdnQYenM@Asurada-Nvidia> (raw)
In-Reply-To: <20250530093512.3959484-4-zhenzhong.duan@intel.com>
On Fri, May 30, 2025 at 05:35:11PM +0800, Zhenzhong Duan wrote:
> Implement [at|de]tach_hwpt handlers in VFIO subsystem. vIOMMU
> utilizes them to attach to or detach from hwpt on host side.
>
> Signed-off-by: Yi Liu <yi.l.liu@intel.com>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> Reviewed-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
> +static bool
> +host_iommu_device_iommufd_vfio_attach_hwpt(HostIOMMUDeviceIOMMUFD *idev,
> + uint32_t hwpt_id, Error **errp)
> +{
> + VFIODevice *vbasedev = HOST_IOMMU_DEVICE(idev)->agent;
> +
> + return !iommufd_cdev_attach_ioas_hwpt(vbasedev, hwpt_id, errp);
> +}
> +
> +static bool
> +host_iommu_device_iommufd_vfio_detach_hwpt(HostIOMMUDeviceIOMMUFD *idev,
> + Error **errp)
> +{
> + VFIODevice *vbasedev = HOST_IOMMU_DEVICE(idev)->agent;
> +
> + return iommufd_cdev_detach_ioas_hwpt(vbasedev, errp);
> +}
Could be a separate patch though:
So, we have the attach API returning "int" while the detach API
returning "bool". Is errno returned back to the attach caller(s)
so the attach API can be a "bool" type too?
Nicolin
next prev parent reply other threads:[~2025-05-30 20:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 9:35 [PATCH v2 0/4] VFIO and IOMMU prerequisite stuff for IOMMU nesting support Zhenzhong Duan
2025-05-30 9:35 ` [PATCH v2 1/4] backends/iommufd: Add a helper to invalidate user-managed HWPT Zhenzhong Duan
2025-06-01 13:57 ` Cédric Le Goater
2025-06-03 12:21 ` Eric Auger
2025-06-04 5:50 ` Duan, Zhenzhong
2025-06-04 17:26 ` Eric Auger
2025-05-30 9:35 ` [PATCH v2 2/4] vfio/iommufd: Add properties and handlers to TYPE_HOST_IOMMU_DEVICE_IOMMUFD Zhenzhong Duan
2025-05-30 21:00 ` Nicolin Chen
2025-06-03 3:12 ` Duan, Zhenzhong
2025-06-03 12:27 ` Eric Auger
2025-05-30 9:35 ` [PATCH v2 3/4] vfio/iommufd: Implement [at|de]tach_hwpt handlers Zhenzhong Duan
2025-05-30 20:31 ` Nicolin Chen via [this message]
2025-06-03 3:03 ` Duan, Zhenzhong
2025-06-03 17:38 ` Eric Auger
2025-05-30 9:35 ` [PATCH v2 4/4] vfio/iommufd: Save vendor specific device info Zhenzhong Duan
2025-05-30 21:05 ` Nicolin Chen
2025-06-03 3:50 ` Duan, Zhenzhong
2025-06-03 12:40 ` Eric Auger
2025-06-04 3:41 ` Duan, Zhenzhong
2025-06-01 18:04 ` [PATCH v2 0/4] VFIO and IOMMU prerequisite stuff for IOMMU nesting support Cédric Le Goater
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=aDoVoaWGIdnQYenM@Asurada-Nvidia \
--to=qemu-devel@nongnu.org \
--cc=alex.williamson@redhat.com \
--cc=chao.p.peng@intel.com \
--cc=clement.mathieu--drif@eviden.com \
--cc=clg@redhat.com \
--cc=ddutile@redhat.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=peterx@redhat.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--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).