From: Bob Liu <bob.liu@oracle.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "jgross@suse.com" <jgross@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"annie.li@oracle.com" <annie.li@oracle.com>,
Ian Jackson <Ian.Jackson@citrix.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [RFC PATCH] blkif.h: document scsi/0x12/0x83 node
Date: Thu, 17 Mar 2016 13:04:20 +0800 [thread overview]
Message-ID: <56EA3AD4.4060103@oracle.com> (raw)
In-Reply-To: <60c0fa3b898c4ba5915dbf12d0413644@AMSPEX02CL03.citrite.net>
On 03/16/2016 10:07 PM, Paul Durrant wrote:
>> -----Original Message-----
>> From: Bob Liu [mailto:bob.liu@oracle.com]
..snip..
>>>
>>
>> But we'd like to get the VPD information(of underlying storage device) also in
>> Linux blkfront, even blkfront is not a SCSI device.
>>
>> That's because our underlying storage device has some vendor-specific
>> features which can be recognized through informations in VPD pages.
>> And Our applications in guest want to aware of these vendor-specific
>> features.
>
> I think the missing piece of the puzzle is how the applications get this information.
> In Windows, since everything is a SCSI LUN (or has to emulate one) applications just send down 'scsi pass-through' IOCTLs and get the raw INQUIRY data back.
> In Linux there would need to be some alternative scheme that presumably blkfront would have to support.
>
They plan to send a REQ_TYPE_BLOCK_PC request down to blkfront, and hoping blkfront can handle this request and return the VPD informations.
I'll confirm weather they can read the xenstore node directly.
--
Regards,
-Bob
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-17 5:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 3:09 [RFC PATCH] blkif.h: document scsi/0x12/0x83 node Bob Liu
2016-03-16 7:16 ` Konrad Rzeszutek Wilk
2016-03-16 12:36 ` Ian Jackson
2016-03-16 13:59 ` Bob Liu
2016-03-16 14:07 ` Paul Durrant
2016-03-17 5:04 ` Bob Liu [this message]
2016-03-16 14:32 ` David Vrabel
2016-03-17 5:07 ` Bob Liu
2016-03-17 11:12 ` Ian Jackson
2016-03-17 11:18 ` David Vrabel
2016-03-17 11:20 ` Ian Jackson
2016-03-22 12:55 ` Bob Liu
2016-03-22 13:41 ` David Vrabel
2016-03-22 14:10 ` Konrad Rzeszutek Wilk
2016-03-22 14:38 ` David Vrabel
2016-03-22 14:43 ` Paul Durrant
2016-03-22 15:09 ` Ian Jackson
2016-03-22 15:25 ` Paul Durrant
2016-03-22 16:14 ` Ian Jackson
2016-03-22 16:50 ` Konrad Rzeszutek Wilk
2016-03-22 17:39 ` Paul Durrant
2016-03-22 15:12 ` Ian Jackson
2016-03-22 15:27 ` Konrad Rzeszutek Wilk
2016-03-22 16:11 ` Ian Jackson
2016-03-22 16:38 ` Konrad Rzeszutek Wilk
2016-03-22 16:25 ` Jan Beulich
2016-03-16 14:33 ` Ian Jackson
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=56EA3AD4.4060103@oracle.com \
--to=bob.liu@oracle.com \
--cc=Ian.Jackson@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=annie.li@oracle.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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 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.