From: Olaf Hering <olaf@aepfle.de>
To: "Alex Ng (LIS)" <alexng@microsoft.com>
Cc: KY Srinivasan <kys@microsoft.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"apw@canonical.com" <apw@canonical.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"leann.ogasawara@canonical.com" <leann.ogasawara@canonical.com>
Subject: Re: [PATCH 3/3] Drivers: hv: utils: Support TimeSync version 4.0 protocol samples.
Date: Wed, 14 Sep 2016 14:57:10 +0200 [thread overview]
Message-ID: <20160914125710.GA12274@aepfle.de> (raw)
In-Reply-To: <DM5PR03MB27300928557066E872D71B22D8FE0@DM5PR03MB2730.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On Tue, Sep 13, Alex Ng (LIS) wrote:
> > On Thu, Sep 08, kys@exchange.microsoft.com wrote:
> > Perhaps a better approach would be to list the known existing hosts and use
> > the new protocol for upcoming, unknown hosts via 'default:'.
> This is a good idea. I will create another patch that addresses this.
I think this variant would cover upcoming hosts for an old kernel:
switch (vmbus_proto_version) {
case 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_WIN7:
case VERSION_WIN8:
case VERSION_WIN8_1:
util_fw_version = UTIL_FW_VERSION;
sd_srv_version = SD_VERSION;
ts_srv_version = TS_VERSION_3;
hb_srv_version = HB_VERSION;
break;
case VERSION_WIN10:
default:
util_fw_version = UTIL_FW_VERSION;
sd_srv_version = SD_VERSION;
ts_srv_version = TS_VERSION;
hb_srv_version = HB_VERSION;
break;
}
Olaf
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
prev parent reply other threads:[~2016-09-14 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 12:23 [PATCH 0/3] Drivers: hv: util: Support the latest time synch protocol from the host kys
2016-09-08 12:24 ` [PATCH 1/3] Drivers: hv: utils: Rename version definitions to reflect protocol version kys
2016-09-08 12:24 ` [PATCH 2/3] Drivers: hv: utils: Use TimeSync samples to adjust the clock after boot kys
2016-09-08 12:24 ` [PATCH 3/3] Drivers: hv: utils: Support TimeSync version 4.0 protocol samples kys
2016-09-13 17:38 ` Olaf Hering
2016-09-13 18:27 ` Alex Ng (LIS)
2016-09-14 12:57 ` Olaf Hering [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=20160914125710.GA12274@aepfle.de \
--to=olaf@aepfle.de \
--cc=alexng@microsoft.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkuznets@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.