From: Ian Campbell <ian.campbell@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v3 4/4] libxl: add support for vscsi
Date: Wed, 11 Mar 2015 16:09:30 +0000 [thread overview]
Message-ID: <1426090170.21353.299.camel@citrix.com> (raw)
In-Reply-To: <20150311160213.GA3063@aepfle.de>
On Wed, 2015-03-11 at 17:02 +0100, Olaf Hering wrote:
> On Wed, Mar 11, Ian Campbell wrote:
>
> > On Fri, 2015-03-06 at 10:45 +0100, Olaf Hering wrote:
> > > +void libxl_device_vscsi_append_dev(libxl_ctx *ctx, libxl_device_vscsi *hst,
> > > + libxl_vscsi_dev *dev);
> > > +int libxl_device_vscsi_get_host(libxl_ctx *ctx,
> > > + uint32_t domid,
> > > + const char *cfg,
> > > + libxl_device_vscsi **vscsi_host);
> > What do these two non-standard functions do?
> >
> > In general the caller would be expected to provide a libxl_device_vscsi,
> > which will be filled in, rather than having the function allocate one.
> >
> > > +int libxl_device_vscsi_parse(libxl_ctx *ctx, const char *cfg,
> > > + libxl_device_vscsi *vscsi_host,
> > > + libxl_vscsi_dev *vscsi_dev);
> >
> > Like with disk, this is xend/xl specific but might be of use to other
> > toolstacks, therefore it belongs in libxlu not in libxl proper.
> > (this might apply to get_host too, depending on what it does)
>
> libvirt for example will do the very same what xl currently does. But so
> far I did not get to libvirt yet. The interface is not finished yet.
That sort of "libvirt uses some xm/xl style syntax" is exactly why
libxlu exists.
next prev parent reply other threads:[~2015-03-11 16:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 9:45 [PATCH v3 0/4] libbxl: add support for pvscsi, iteration 3 Olaf Hering
2015-03-06 9:45 ` [PATCH v3 1/4] vscsiif.h: fix WWN notation for p-dev property Olaf Hering
2015-03-06 9:45 ` [PATCH v3 2/4] docs: add vscsi to xenstore-paths.markdown Olaf Hering
2015-03-06 13:55 ` Wei Liu
2015-03-06 15:07 ` Olaf Hering
2015-03-06 9:45 ` [PATCH v3 3/4] docs: add pvscsi.txt Olaf Hering
2015-03-06 13:55 ` Wei Liu
2015-03-06 15:11 ` Olaf Hering
2015-03-06 15:37 ` Wei Liu
2015-03-11 15:23 ` Ian Campbell
2015-03-06 9:45 ` [PATCH v3 4/4] libxl: add support for vscsi Olaf Hering
2015-03-06 14:31 ` Wei Liu
2015-03-06 15:25 ` Olaf Hering
2015-03-06 15:53 ` Wei Liu
2015-03-09 16:08 ` Olaf Hering
2015-03-09 16:46 ` Wei Liu
2015-03-11 15:24 ` Ian Campbell
2015-03-11 15:33 ` Ian Campbell
2015-03-11 16:02 ` Olaf Hering
2015-03-11 16:09 ` Ian Campbell [this message]
2015-03-13 13:49 ` Olaf Hering
2015-03-11 16:06 ` Olaf Hering
2015-03-12 16:07 ` Olaf Hering
2015-03-12 16:47 ` Ian Campbell
2015-03-13 13:45 ` Olaf Hering
2015-03-13 15:10 ` Wei Liu
2015-03-16 8:16 ` Olaf Hering
2015-03-16 11:30 ` Wei Liu
2015-03-12 16:20 ` Olaf Hering
2015-03-12 16:46 ` Ian Campbell
2015-03-13 13:44 ` Olaf Hering
2015-03-13 14:18 ` Ian Campbell
2015-03-26 12:55 ` Olaf Hering
2015-03-26 13:46 ` Ian Campbell
2015-03-27 7:38 ` Olaf Hering
2015-04-10 9:23 ` wating for backend changes (was Re: [PATCH v3 4/4] libxl: add support for vscsi) Olaf Hering
2015-04-14 15:55 ` Olaf Hering
2015-04-15 11:50 ` 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=1426090170.21353.299.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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.