[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aHAF2ATrZUIFCf+e@Asurada-Nvidia>
Date: Thu, 10 Jul 2025 11:26:32 -0700
From: Nicolin Chen <nicolinc@...dia.com>
To: Xu Yilun <yilun.xu@...ux.intel.com>
CC: <jgg@...dia.com>, <jgg@...pe.ca>, <kevin.tian@...el.com>,
<will@...nel.org>, <aneesh.kumar@...nel.org>, <iommu@...ts.linux.dev>,
<linux-kernel@...r.kernel.org>, <joro@...tes.org>, <robin.murphy@....com>,
<shuah@...nel.org>, <aik@....com>, <dan.j.williams@...el.com>,
<baolu.lu@...ux.intel.com>, <yilun.xu@...el.com>
Subject: Re: [PATCH v4 1/7] iommufd/viommu: Roll back to use
iommufd_object_alloc() for vdevice
On Wed, Jul 09, 2025 at 12:02:28PM +0800, Xu Yilun wrote:
> To solve the vdevice lifecycle issue, future patches make the vdevice
> allocation protected by lock. That will make
> iommufd_object_alloc_ucmd() not applicable for vdevice. Roll back to
> use iommufd_object_alloc() for preparation.
>
> Signed-off-by: Xu Yilun <yilun.xu@...ux.intel.com>
Reviewed-by: Nicolin Chen <nicolinc@...dia.com>
Powered by blists - more mailing lists