Message ID | 20241124070808.194860-1-avri.altman@wdc.com |
---|---|
Headers | show |
Series | Untie the host lock entanglement - part 2 | expand |
Avri, > Here is the 2nd part in the sequel, watering down the scsi host lock > usage in the ufs driver. This work is motivated by a comment made by > Bart [1], of the abuse of the scsi host lock in the ufs driver. Its > Precursor [2] removed the host lock around some of the host register > accesses. > > This part replaces the scsi host lock by dedicated locks serializing > access to the clock gating and clock scaling members. Applied to 6.14/scsi-staging, thanks!
On Sun, 24 Nov 2024 09:08:04 +0200, Avri Altman wrote: > Here is the 2nd part in the sequel, watering down the scsi host lock > usage in the ufs driver. This work is motivated by a comment made by > Bart [1], of the abuse of the scsi host lock in the ufs driver. Its > Precursor [2] removed the host lock around some of the host register > accesses. > > This part replaces the scsi host lock by dedicated locks serializing > access to the clock gating and clock scaling members. > > [...] Applied to 6.14/scsi-queue, thanks! [1/4] scsi: ufs: core: Introduce ufshcd_has_pending_tasks https://git.kernel.org/mkp/scsi/c/e738ba458e75 [2/4] scsi: ufs: core: Prepare to introduce a new clock_gating lock https://git.kernel.org/mkp/scsi/c/7869c6521f57 [3/4] scsi: ufs: core: Introduce a new clock_gating lock https://git.kernel.org/mkp/scsi/c/209f4e43b806 [4/4] scsi: ufs: core: Introduce a new clock_scaling lock https://git.kernel.org/mkp/scsi/c/be769e5cf53b