RE: [PATCH v4 03/23] iommufd/viommu: Allow driver-specific user data for a vIOMMU object

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Nicolin Chen <nicolinc@xxxxxxxxxx>, "jgg@xxxxxxxxxx" <jgg@xxxxxxxxxx>, "corbet@xxxxxxx" <corbet@xxxxxxx>, "will@xxxxxxxxxx" <will@xxxxxxxxxx>
Subject: RE: [PATCH v4 03/23] iommufd/viommu: Allow driver-specific user data for a vIOMMU object
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Thu, 15 May 2025 05:45:40 +0000
Accept-language: en-US
Cc: "bagasdotme@xxxxxxxxx" <bagasdotme@xxxxxxxxx>, "robin.murphy@xxxxxxx" <robin.murphy@xxxxxxx>, "joro@xxxxxxxxxx" <joro@xxxxxxxxxx>, "thierry.reding@xxxxxxxxx" <thierry.reding@xxxxxxxxx>, "vdumpa@xxxxxxxxxx" <vdumpa@xxxxxxxxxx>, "jonathanh@xxxxxxxxxx" <jonathanh@xxxxxxxxxx>, "shuah@xxxxxxxxxx" <shuah@xxxxxxxxxx>, "jsnitsel@xxxxxxxxxx" <jsnitsel@xxxxxxxxxx>, "nathan@xxxxxxxxxx" <nathan@xxxxxxxxxx>, "peterz@xxxxxxxxxxxxx" <peterz@xxxxxxxxxxxxx>, "Liu, Yi L" <yi.l.liu@xxxxxxxxx>, "mshavit@xxxxxxxxxx" <mshavit@xxxxxxxxxx>, "praan@xxxxxxxxxx" <praan@xxxxxxxxxx>, "zhangzekun11@xxxxxxxxxx" <zhangzekun11@xxxxxxxxxx>, "iommu@xxxxxxxxxxxxxxx" <iommu@xxxxxxxxxxxxxxx>, "linux-doc@xxxxxxxxxxxxxxx" <linux-doc@xxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "linux-arm-kernel@xxxxxxxxxxxxxxxxxxx" <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>, "linux-tegra@xxxxxxxxxxxxxxx" <linux-tegra@xxxxxxxxxxxxxxx>, "linux-kselftest@xxxxxxxxxxxxxxx" <linux-kselftest@xxxxxxxxxxxxxxx>, "patches@xxxxxxxxxxxxxxx" <patches@xxxxxxxxxxxxxxx>, "mochs@xxxxxxxxxx" <mochs@xxxxxxxxxx>, "alok.a.tiwari@xxxxxxxxxx" <alok.a.tiwari@xxxxxxxxxx>, "vasant.hegde@xxxxxxx" <vasant.hegde@xxxxxxx>
In-reply-to: <86b279e902a3fe624ca9261b84f378d62c5049e8.1746757630.git.nicolinc@nvidia.com>
References: <cover.1746757630.git.nicolinc@nvidia.com> <86b279e902a3fe624ca9261b84f378d62c5049e8.1746757630.git.nicolinc@nvidia.com>

> From: Nicolin Chen <nicolinc@xxxxxxxxxx>
> Sent: Friday, May 9, 2025 11:02 AM
> 
> + * @data_len: Length of the type specific data
> + * @__reserved: Must be 0
> + * @data_uptr: User pointer to an array of driver-specific virtual IOMMU
> data

I don't think there is 'an array'.

Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx>

Follow-Ups:
- Re: [PATCH v4 03/23] iommufd/viommu: Allow driver-specific user data for a vIOMMU object
  - From: Nicolin Chen

References:
- [PATCH v4 00/23] iommufd: Add vIOMMU infrastructure (Part-4 HW QUEUE)
  - From: Nicolin Chen
- [PATCH v4 03/23] iommufd/viommu: Allow driver-specific user data for a vIOMMU object
  - From: Nicolin Chen

Prev by Date: RE: [PATCH v4 02/23] iommu: Pass in a driver-level user data structure to viommu_alloc op
Next by Date: RE: [PATCH v4 04/23] iommu: Add iommu_copy_struct_to_user helper
Previous by thread: [PATCH v4 03/23] iommufd/viommu: Allow driver-specific user data for a vIOMMU object
Next by thread: Re: [PATCH v4 03/23] iommufd/viommu: Allow driver-specific user data for a vIOMMU object
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite Forum] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [Linux Resources]