linux-kernel - Re: [PATCH v8 00/29] iommufd: Add vIOMMU infrastructure (Part-4 HW QUEUE)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250709173318.GI1599700@nvidia.com>
Date: Wed, 9 Jul 2025 14:33:18 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Nicolin Chen <nicolinc@...dia.com>
Cc: kevin.tian@...el.com, corbet@....net, will@...nel.org,
	bagasdotme@...il.com, robin.murphy@....com, joro@...tes.org,
	thierry.reding@...il.com, vdumpa@...dia.com, jonathanh@...dia.com,
	shuah@...nel.org, jsnitsel@...hat.com, nathan@...nel.org,
	peterz@...radead.org, yi.l.liu@...el.com, mshavit@...gle.com,
	praan@...gle.com, zhangzekun11@...wei.com, iommu@...ts.linux.dev,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-tegra@...r.kernel.org,
	linux-kselftest@...r.kernel.org, patches@...ts.linux.dev,
	mochs@...dia.com, alok.a.tiwari@...cle.com, vasant.hegde@....com,
	dwmw2@...radead.org, baolu.lu@...ux.intel.com
Subject: Re: [PATCH v8 00/29] iommufd: Add vIOMMU infrastructure (Part-4 HW
 QUEUE)

On Fri, Jul 04, 2025 at 06:13:16PM -0700, Nicolin Chen wrote:
> Nicolin Chen (29):
>   iommufd: Report unmapped bytes in the error path of
>     iopt_unmap_iova_range
>   iommufd: Correct virt_id kdoc at struct iommu_vdevice_alloc
>   iommufd/viommu: Explicitly define vdev->virt_id
>   iommu: Use enum iommu_hw_info_type for type in hw_info op
>   iommu: Add iommu_copy_struct_to_user helper
>   iommu: Pass in a driver-level user data structure to viommu_init op
>   iommufd/viommu: Allow driver-specific user data for a vIOMMU object
>   iommufd/selftest: Support user_data in mock_viommu_alloc
>   iommufd/selftest: Add coverage for viommu data
>   iommufd/access: Add internal APIs for HW queue to use
>   iommufd/access: Bypass access->ops->unmap for internal use
>   iommufd/viommu: Add driver-defined vDEVICE support
>   iommufd/viommu: Introduce IOMMUFD_OBJ_HW_QUEUE and its related struct
>   iommufd/viommu: Add IOMMUFD_CMD_HW_QUEUE_ALLOC ioctl
>   iommufd/driver: Add iommufd_hw_queue_depend/undepend() helpers
>   iommufd/selftest: Add coverage for IOMMUFD_CMD_HW_QUEUE_ALLOC
>   iommufd: Add mmap interface
>   iommufd/selftest: Add coverage for the new mmap interface
>   Documentation: userspace-api: iommufd: Update HW QUEUE
>   iommu: Allow an input type in hw_info op
>   iommufd: Allow an input data_type via iommu_hw_info
>   iommufd/selftest: Update hw_info coverage for an input data_type
>   iommu/arm-smmu-v3-iommufd: Add vsmmu_size/type and vsmmu_init impl ops
>   iommu/arm-smmu-v3-iommufd: Add hw_info to impl_ops
>   iommu/tegra241-cmdqv: Use request_threaded_irq
>   iommu/tegra241-cmdqv: Simplify deinit flow in
>     tegra241_cmdqv_remove_vintf()
>   iommu/tegra241-cmdqv: Do not statically map LVCMDQs
>   iommu/tegra241-cmdqv: Add user-space use support
>   iommu/tegra241-cmdqv: Add IOMMU_VEVENTQ_TYPE_TEGRA241_CMDQV support

I've dropped this in linux-next with the little fix I mentioned.

If there are further remarks before the merge window please send a v9

Thanks,
Jason