summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorK. Y. Srinivasan <kys@microsoft.com>2014-01-16 11:59:58 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-02-22 12:41:28 -0800
commit3339d76f6c82371e4546735dab7a00db4bfb14d5 (patch)
tree5b23bef5d748264f6b3269466a7d367c14e8f778 /include
parentc7677684ab70aff2f5f514f8827d315833bc6ac3 (diff)
downloadlinux-3.10-3339d76f6c82371e4546735dab7a00db4bfb14d5.tar.gz
linux-3.10-3339d76f6c82371e4546735dab7a00db4bfb14d5.tar.bz2
linux-3.10-3339d76f6c82371e4546735dab7a00db4bfb14d5.zip
Drivers: hv: vmbus: Don't timeout during the initial connection with host
commit 269f979467cf49f2ea8132316c1f00f8c9678f7c upstream. When the guest attempts to connect with the host when there may already be a connection with the host (as would be the case during the kdump/kexec path), it is difficult to guarantee timely response from the host. Starting with WS2012 R2, the host supports this ability to re-connect with the host (explicitly to support kexec). Prior to responding to the guest, the host needs to ensure that device states based on the previous connection to the host have been properly torn down. This may introduce unbounded delays. To deal with this issue, don't do a timed wait during the initial connect with the host. Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions