[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN9PR11MB5276FEBFFEACE603E45517898CE72@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Mon, 20 Jan 2025 05:37:13 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Nicolin Chen <nicolinc@...dia.com>, "jgg@...dia.com" <jgg@...dia.com>
CC: "joro@...tes.org" <joro@...tes.org>, "will@...nel.org" <will@...nel.org>,
"robin.murphy@....com" <robin.murphy@....com>, "baolu.lu@...ux.intel.com"
<baolu.lu@...ux.intel.com>, "iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH rc v4] iommufd/fault: Use a separate spinlock to protect
fault->deliver list
> From: Nicolin Chen <nicolinc@...dia.com>
> Sent: Saturday, January 18, 2025 3:29 AM
>
>
> Lastly, move the mutex closer to the response in the fault structure,
> and update its kdoc accordingly.
Then this comment is stale.
>
> - /* The lists of outstanding faults protected by below mutex. */
> - struct mutex mutex;
> + spinlock_t lock; /* protects the deliver list */
> struct list_head deliver;
> + struct mutex mutex; /* serializes response flows */
> struct xarray response;
>
And the comment for the mutex should be restored.
Powered by blists - more mailing lists