From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: "Alex Ng \(LIS\)" <alexng@microsoft.com>
Cc: "devel\@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"KY Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH] hv: utils: properly pick TS protocol version for future hosts
Date: Tue, 29 Nov 2016 09:38:37 +0100 [thread overview]
Message-ID: <878ts2fzoy.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <MWHPR03MB2734E0222C1E962275BF574DD88A0@MWHPR03MB2734.namprd03.prod.outlook.com> (Alex Ng's message of "Mon, 28 Nov 2016 18:16:49 +0000")
"Alex Ng (LIS)" <alexng@microsoft.com> writes:
>> -----Original Message-----
>> From: Vitaly Kuznetsov [mailto:vkuznets@redhat.com]
>> Sent: Monday, November 28, 2016 8:30 AM
>> To: devel@linuxdriverproject.org
>> Cc: linux-kernel@vger.kernel.org; KY Srinivasan <kys@microsoft.com>;
>> Haiyang Zhang <haiyangz@microsoft.com>; Alex Ng (LIS)
>> <alexng@microsoft.com>
>> Subject: [PATCH] hv: utils: properly pick TS protocol version for future hosts
>>
>> It is reasonable to expect that future Hyper-V versions will continue
>> supporting TimeSync v4 protocol, we, however, only pick it for
>> VERSION_WIN10. Currently this is not an issue as VERSION_WIN10 is the
>> maximum protocol version we can negotiate but this may change in future.
>> Instead of hoping that we won't forget to update it when time comes I
>> suggest we change the default now.
>>
>
> Vitaly, can you see if this upstream commit already fixes the issue you described?
>
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=3da0401b4d0e17aea7526db0235d98fa535d903e
>
Yes, thanks, missied it!
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>> ---
>> drivers/hv/hv_util.c | 13 +++++--------
>> 1 file changed, 5 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
>> index bcd0630..a13003f 100644
>> --- a/drivers/hv/hv_util.c
>> +++ b/drivers/hv/hv_util.c
>> @@ -382,23 +382,20 @@ static int util_probe(struct hv_device *dev,
>> * Based on the host; initialize the framework and
>> * service version numbers we will negotiate.
>> */
>> - switch (vmbus_proto_version) {
>> - case (VERSION_WS2008):
>> + if (vmbus_proto_version <= VERSION_WS2008) {
>> util_fw_version = UTIL_WS2K8_FW_VERSION;
>> sd_srv_version = SD_VERSION_1;
>> ts_srv_version = TS_VERSION_1;
>> hb_srv_version = HB_VERSION_1;
>> - break;
>> - case(VERSION_WIN10):
>> + } else if (vmbus_proto_version < VERSION_WIN10) {
>> util_fw_version = UTIL_FW_VERSION;
>> sd_srv_version = SD_VERSION;
>> - ts_srv_version = TS_VERSION;
>> + ts_srv_version = TS_VERSION_3;
>> hb_srv_version = HB_VERSION;
>> - break;
>> - default:
>> + } else {
>> util_fw_version = UTIL_FW_VERSION;
>> sd_srv_version = SD_VERSION;
>> - ts_srv_version = TS_VERSION_3;
>> + ts_srv_version = TS_VERSION;
>> hb_srv_version = HB_VERSION;
>> }
>>
>> --
>> 2.9.3
--
Vitaly
prev parent reply other threads:[~2016-11-29 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 16:30 Vitaly Kuznetsov
2016-11-28 18:16 ` Alex Ng (LIS)
2016-11-29 8:38 ` Vitaly Kuznetsov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ts2fzoy.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=alexng@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome