From: Olaf Hering <olaf@aepfle.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Keir Fraser <keir@xen.org>,
Ian Campbell <ian.campbell@citrix.com>, Tim Deegan <tim@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v3 3/4] docs: add pvscsi.txt
Date: Fri, 6 Mar 2015 16:11:20 +0100 [thread overview]
Message-ID: <20150306151120.GC21639@aepfle.de> (raw)
In-Reply-To: <20150306135549.GT12103@zion.uk.xensource.com>
On Fri, Mar 06, Wei Liu wrote:
> On Fri, Mar 06, 2015 at 10:45:55AM +0100, Olaf Hering wrote:
> > +== TODO ===
> > +
> > +How to do live migration?
> > + - pdev will likely be evaluated again on the target host if it came from
> > + domU.cfg. But what about pdev from 'xl scsi-attach pdev vdev'? Its required
> > + to adjust h:c:t:l on the target host.
> > +
> > +How to handle FIXME in libxl_retrieve_domain_configuration?
> > + - "MERGE(vscsi, vscsis, COMPARE_DEVID, {});", when does this code run?
> > +
>
> I don't think this kind of information that relates to libxl internal
> belongs here.
Its the overall TODO list, it has to go somewhere. And it will be
removed once its empty.
> Anyway, to answer you question. libxl_retrieve_domain_configuration is
> called by xl when you do migration / detailed domain configuration
> listing etc.
How can the values diverge? With commands like 'scsi-attach'?
> I think the comment above MERGE macro states what it does and how to use
> it. Is there anything that's not clear to you?
I think for vscsi it has to compare the vdev h:c:t:l part, just as disk
compares xvda. I will look at this once I'm done with libvirt
integration.
Olaf
next prev parent reply other threads:[~2015-03-06 15:11 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 [this message]
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
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=20150306151120.GC21639@aepfle.de \
--to=olaf@aepfle.de \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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.