From: Sitsofe Wheeler <sitsofe@gmail.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: Long Li <longli@microsoft.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"JBottomley@parallels.com" <JBottomley@parallels.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi:storvsc enable reading from VPD pages on SPC-2
Date: Thu, 11 Dec 2014 10:53:45 +0000 [thread overview]
Message-ID: <20141211101945.GA25624@sucs.org> (raw)
In-Reply-To: <BY2PR0301MB0711CF1C9FBD8EFED89B3911A0620@BY2PR0301MB0711.namprd03.prod.outlook.com>
On Wed, Dec 10, 2014 at 11:30:30PM +0000, KY Srinivasan wrote:
>
> > >
> > > + {"Msft", "Virtual Disk", "1.0", BLIST_TRY_VPD_PAGES},
> > >
> > > Is that version field meaningful or is it safe for us to inquire about
> > > VPD pages without problems on older versions?
> >
> > This version is used in all current Hyper-V hosts: Windows 2008 R2, 2012 and
> > 2012 R2. However it may change in future Windows releases.
>
> The next version of the host will be claiming conformance to SPC-3
Will the version number ("1.0") of Virtual Disks also be changed? Part
of me hopes it will as it will mean certain quirks for virtual disks
will be easier to apply and won't need host version (are you 2008, 2012,
2016) version logic...
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2014-12-11 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 8:38 [PATCH] scsi:storvsc enable reading from VPD pages on SPC-2 Long Li
2014-12-10 20:57 ` Sitsofe Wheeler
2014-12-10 22:33 ` Long Li
2014-12-10 21:12 ` Martin K. Petersen
2014-12-10 22:28 ` Long Li
2014-12-10 23:30 ` KY Srinivasan
2014-12-11 10:53 ` Sitsofe Wheeler [this message]
2014-12-11 18:49 ` KY Srinivasan
2014-12-12 3:03 ` Martin K. Petersen
2014-12-16 2:11 ` Long Li
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=20141211101945.GA25624@sucs.org \
--to=sitsofe@gmail.com \
--cc=JBottomley@parallels.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox