From: David Vrabel <david.vrabel@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: jgross@suse.com, annie.li@oracle.com, xen-devel@lists.xen.org,
Paul.Durrant@citrix.com, roger.pau@citrix.com
Subject: Re: [RFC PATCH] blkif.h: document scsi/0x12/0x83 node
Date: Thu, 17 Mar 2016 11:18:30 +0000 [thread overview]
Message-ID: <56EA9286.5080109@citrix.com> (raw)
In-Reply-To: <22250.37170.872699.326005@mariner.uk.xensource.com>
On 17/03/16 11:12, Ian Jackson wrote:
> David Vrabel writes ("Re: [Xen-devel] [RFC PATCH] blkif.h: document scsi/0x12/0x83 node"):
>> On 16/03/16 13:59, Bob Liu wrote:
>>> But we'd like to get the VPD information(of underlying storage device) also in Linux blkfront, even blkfront is not a SCSI device.
>>
>> Why does blkback/blkfront need to involved here? This is just some
>> xenstore keys that can be written by the toolstack and directly read by
>> the relevant application in the guest.
>
> I'm getting rather a different picture here than at first. Previously
> I thought you had some 3rd-party application, not under your control,
> which expected to see this VPD data.
Bob != David?
> But now I think that you're saying the application is under your own
> control. I don't understand why synthetic VPD data is the best way to
> give your application the information it needs.
>
> What is the application doing with this VPD data ? I mean,
> which specific application functions, and how do they depend on the
> VPD data ?
David
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-17 11:18 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
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 [this message]
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=56EA9286.5080109@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Jackson@eu.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.