On Fri, Jun 19, 2020 at 10:58:40PM -0400, Martin K. Petersen wrote:
>
> Andrea,
>
> >> This patch should go via the hyperv tree because a later patch is
> >> dependent on it. It requires and ack from SCSI maintainers though.
>
> Looks OK to me.
>
> Acked-by: Martin K. Petersen
Thanks Martin.
Andrea,
>> This patch should go via the hyperv tree because a later patch is
>> dependent on it. It requires and ack from SCSI maintainers though.
Looks OK to me.
Acked-by: Martin K. Petersen
--
Martin K. Petersen Oracle Linux Engineering
On Fri, Jun 19, 2020 at 04:01:36PM +, Wei Liu wrote:
> Cc SCSI maintainers
>
> This patch should go via the hyperv tree because a later patch is
> dependent on it. It requires and ack from SCSI maintainers though.
Right. Sorry for the Cc: omission... ;-/
SCSI maintainers, please let me kno
Cc SCSI maintainers
This patch should go via the hyperv tree because a later patch is
dependent on it. It requires and ack from SCSI maintainers though.
Thanks,
Wei.
On Wed, Jun 17, 2020 at 06:46:41PM +0200, Andrea Parri (Microsoft) wrote:
> storvsc uses the spinlock of the hv_device's primary c
From: Andrea Parri (Microsoft) Sent: Wednesday, June
17, 2020 9:47 AM
>
> storvsc uses the spinlock of the hv_device's primary channel to
> serialize modifications of stor_chns[] performed by storvsc_do_io()
> and storvsc_change_target_cpu(), when it could/should use a (per-)
> storvsc_device sp
storvsc uses the spinlock of the hv_device's primary channel to
serialize modifications of stor_chns[] performed by storvsc_do_io()
and storvsc_change_target_cpu(), when it could/should use a (per-)
storvsc_device spinlock: this change untangles the synchronization
mechanism for the (storvsc-specif
6 matches
Mail list logo
