Does this mean that host-to guest timesync now works properly with Linux
guests?
-- Jeff
-Original Message-
From: linux-kernel-ow...@vger.kernel.org
[mailto:linux-kernel-ow...@vger.kernel.org]
On Behalf Of K. Y. Srinivasan
Sent: Tuesday, December 2, 2014 17:04
To: x...@kernel.org;
We have had the Hyper-V clocksource for sometime now and this patch
just marks this
clocksource as being continuous. Nothing has changed with regards to
timesynch.
Alright, that cleared up that question. Gleaning around from the source
tree, I don't seem to
comprehend what changes are being
Is it OK to replace a scsi_level of SCSI-2 with SCSI_SPC_3? Additionally is
it also OK to force
SCSI_SPC_3 on Hyper-V 2008?
I would patch the driver accordingly to force the SPC-3 flag.
For a Win2k8 host, I don't know what the side effects are, so it's safe to say
it's not a good idea to
compliance for hosts earlier than Win10 also enables
TRIM support.
Suggested by: James Bottomley james.bottom...@hansenpartnership.com
Signed-off-by: Jeff Leung jle...@v10networks.ca
---
drivers/scsi/storvsc_drv.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git
On the current release of Windows (windows 10), we are advertising SPC3
compliance.
We are ok with declaring compliance to SPC3 in our drivers.
If you are going to declare SPC3 compliance in the drivers, are you going to
put in
checks to ensure that SPC-3 compliance doesn't get accidentally
WS2008R2 is a supported platform and it turns out that the maximum
sendbuf
size that ws2008R2 can support is only 15MB. Make the necessary
adjustment.
Signed-off-by: K. Y. Srinivasan k...@microsoft.com
---
drivers/net/hyperv/hyperv_net.h |2 +-
1 files changed, 1 insertions(+), 1
