summaryrefslogtreecommitdiffstats
path: root/drivers/hv/hyperv_vmbus.h
diff options
context:
space:
mode:
authorAndrea Parri (Microsoft) <parri.andrea@gmail.com>2020-04-06 02:15:05 +0200
committerWei Liu <wei.liu@kernel.org>2020-04-23 15:17:11 +0200
commitb9fa1b8797dcb579a9642a502769e1a5c3adc0d2 (patch)
tree30c43007fbb52fdf9fe1346a0a348e881aca7c00 /drivers/hv/hyperv_vmbus.h
parentDrivers: hv: vmbus: Always handle the VMBus messages on CPU0 (diff)
downloadlinux-b9fa1b8797dcb579a9642a502769e1a5c3adc0d2.tar.xz
linux-b9fa1b8797dcb579a9642a502769e1a5c3adc0d2.zip
Drivers: hv: vmbus: Don't bind the offer&rescind works to a specific CPU
The offer and rescind works are currently scheduled on the so called "connect CPU". However, this is not really needed: we can synchronize the works by relying on the usage of the offer_in_progress counter and of the channel_mutex mutex. This synchronization is already in place. So, remove this unnecessary "bind to the connect CPU" constraint and update the inline comments accordingly. Suggested-by: Dexuan Cui <decui@microsoft.com> Signed-off-by: Andrea Parri (Microsoft) <parri.andrea@gmail.com> Link: https://lore.kernel.org/r/20200406001514.19876-3-parri.andrea@gmail.com Reviewed-by: Michael Kelley <mikelley@microsoft.com> Signed-off-by: Wei Liu <wei.liu@kernel.org>
Diffstat (limited to 'drivers/hv/hyperv_vmbus.h')
0 files changed, 0 insertions, 0 deletions