Talos™ II Linux sources for OpenBMC https://git.raptorcs.com/git/talos-obmc-linux/atom?h=v3.12 2013-09-26T21:20:22+00:00 2013-09-26T21:20:22+00:00 K. Y. Srinivasan kys@microsoft.com 2013-09-04T22:41:58+00:00 urn:sha1:8bbf9f440f196ee08cc5ab1c19e62b1c5a736ff0 commit 666b9adc801ef012612c4e43e0f44b2cdc1979cf terminated vmbus version negotiation incorrectly. We need to terminate the version negotiation only if the current negotiation were to timeout. Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Cc: Olaf Hering <ohering@suse.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-09-26T21:20:21+00:00 K. Y. Srinivasan kys@microsoft.com 2013-09-06T18:49:56+00:00 urn:sha1:3a4916050ba2e0f1d114ef540abdf02b2b173e61 The current code does not correctly negotiate the version numbers for the util driver when hosted on earlier hosts. The version numbers presented by this driver were not compatible with the version numbers supported by Windows Server 2008. Fix this problem. I would like to thank Olaf Hering (ohering@suse.com) for identifying the problem. Reported-by: Olaf Hering <ohering@suse.com> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-08-30T19:08:04+00:00 K. Y. Srinivasan kys@microsoft.com 2013-08-28T21:56:54+00:00 urn:sha1:666b9adc801ef012612c4e43e0f44b2cdc1979cf The current code would attempt to negotiate a different protocol version if the current negotiation timed out. This triggers an assert in the host (on debug builds). Avoid this by negotiating a newer version only if the host properly rejects the current version being negotiated. Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-08-28T04:49:26+00:00 K. Y. Srinivasan kys@microsoft.com 2013-08-26T21:08:58+00:00 urn:sha1:42dceebe34600b2d02a38baa3e869009ba3d14c7 The channel state should be correctly set before registering the device. In the current code the driver probe would fail for channels that have been rescinded and subsequently re-offered. Fix the bug. Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Cc: stable <stable@vger.kernel.org> # 3.11 Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-08-02T03:34:30+00:00 Olaf Hering olaf@aepfle.de 2013-05-29T09:29:07+00:00 urn:sha1:cfc25993e81f3fa68481d062be634d33184d5eae Remove HV_DRV_VERSION, it has no meaning for upstream drivers. Initially it was supposed to show the "Linux Integration Services" version, now it is not in sync anymore with the out-of-tree drivers available from the MSFT website. The only place where a version string is still required is the KVP command "IntegrationServicesVersion" which is handled by tools/hv/hv_kvp_daemon.c. To satisfy such KVP request from the host pass the current string to the daemon during KVP userland registration. Signed-off-by: Olaf Hering <olaf@aepfle.de> Acked-by: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-07-29T18:50:17+00:00 Greg Kroah-Hartman gregkh@linuxfoundation.org 2013-07-29T18:50:17+00:00 urn:sha1:9c5891bd4342349a200676d33f742dd1b864822c This resolves a merge issue with: drivers/misc/mei/init.c Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-07-26T23:40:42+00:00 K. Y. Srinivasan kys@microsoft.com 2013-07-18T00:27:27+00:00 urn:sha1:20138d6cb838aa01bb1b382dcb5f3d3a119ff2cb Each message sent from the guest carries with it a transaction ID. Assign the transaction ID just before putting the message on the VMBUS. This would help in debugging on the host side. Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-07-26T23:40:41+00:00 K. Y. Srinivasan kys@microsoft.com 2013-07-02T17:31:30+00:00 urn:sha1:6741335bc7294548ac95cb1f4671991ff30da193 The current code picked the highest version advertised by the host. WS2012 R2 has implemented a protocol version for KVP that is not compatible with prior protocol versions of KVP. Fix the bug in the current code by explicitly specifying the protocol version that the guest can support. Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-07-17T06:19:19+00:00 K. Y. Srinivasan kys@microsoft.com 2013-07-15T05:38:12+00:00 urn:sha1:c5e2254f8d63a6654149aa32ac5f2b7dd66a976d When we are posting pressure status, we may get interrupted and handle the un-balloon operation. In this case just don't post the status as we know the pressure status is stale. Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Cc: Stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2013-07-17T06:19:19+00:00 K. Y. Srinivasan kys@microsoft.com 2013-07-15T05:38:11+00:00 urn:sha1:ed07ec93e83ec471d365ce084e43ad90fd205903 As we hot-add 128 MB chunks of memory, we wait to ensure that the memory is onlined before attempting to hot-add the next chunk. If the udev rule for memory hot-add is not executed within the allowed time, we would rollback the state and abort further hot-add. Since the hot-add has succeeded and the only failure is that the memory is not onlined within the allowed time, we should not be rolling back the state. Fix this bug. Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Cc: Stable <stable@vger.kernel.org> Acked-by: Jason Wang <jasowang@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>