[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A70AC0C1B7E7FD478A6BF19705461AA01109B3@IMBER.smb.curriegrad2004.ca>
Date: Sat, 11 Oct 2014 13:22:11 -0700
From: "Jeff Leung" <jleung@...networks.ca>
To: "KY Srinivasan" <kys@...rosoft.com>,
"James Bottomley" <James.Bottomley@...senPartnership.com>,
"Christoph Hellwig" <hch@...radead.org>
Cc: "Sitsofe Wheeler" <sitsofe@...il.com>,
"Haiyang Zhang" <haiyangz@...rosoft.com>,
"Christoph Hellwig" <hch@....de>, "Hannes Reinecke" <hare@...e.de>,
<linux-scsi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<devel@...uxdriverproject.org>
Subject: RE: [PATCH 0/3] scsi: Add Hyper-V logical block provisioning quirks
> 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 enabled for hypervisors below
Win10?
I do know for a fact that Ubuntu's kernels already force SPC3 compliance to enable specific
features such as TRIM on earlier versions of Hyper-V (Namely Hyper-V 2012 and 2012 R2).
--Jeff
> Regards,
>
> K. Y
>
>
> NryزXvؖ){nlj{zX.}zj:v zZzf~zwڢ).jyA
>
> .i
Powered by blists - more mailing lists