From: Olaf Hering <olaf@aepfle.de>
To: Juergen Gross <jgross@suse.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 3/4] docs: add pvscsi.txt
Date: Mon, 2 Mar 2015 19:24:14 +0100 [thread overview]
Message-ID: <20150302182414.GA16226@aepfle.de> (raw)
In-Reply-To: <54F48340.1070506@suse.com>
On Mon, Mar 02, Juergen Gross wrote:
> On 03/02/2015 04:14 PM, Olaf Hering wrote:
> >In this case the code which checks pdev usage in
> >libxl_device_vscsi_get_host can just be removed.
> Hmm, maybe issuing a warning would be a sensible thing to do?
This gets us back to square #1 with the question how to do
foreach domid ; foreach vscsi
If domains are started parallel a simple check will miss devices.
Perhaps not an issue if its just a warning message.
Olaf
next prev parent reply other threads:[~2015-03-02 18:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 10:15 [PATCH 0/4] libbxl: add support for pvscsi, iteration 2 Olaf Hering
2015-03-02 10:15 ` [PATCH 1/4] vscsiif.h: remove reference to WWN Olaf Hering
2015-03-02 10:46 ` Jan Beulich
2015-03-02 10:50 ` Andrew Cooper
2015-03-02 10:55 ` Jürgen Groß
2015-03-02 11:00 ` Andrew Cooper
2015-03-02 10:59 ` Jan Beulich
2015-03-02 10:59 ` Juergen Gross
2015-03-02 14:34 ` Olaf Hering
2015-03-02 14:40 ` Olaf Hering
2015-03-02 14:55 ` Juergen Gross
2015-03-02 10:16 ` [PATCH 2/4] docs: add vscsi to xenstore-paths.markdown Olaf Hering
2015-03-02 10:16 ` [PATCH 3/4] docs: add pvscsi.txt Olaf Hering
2015-03-02 10:49 ` Jan Beulich
2015-03-02 11:04 ` Juergen Gross
2015-03-02 15:14 ` Olaf Hering
2015-03-02 15:35 ` Juergen Gross
2015-03-02 18:24 ` Olaf Hering [this message]
2015-03-02 10:16 ` [PATCH 4/4] libxl: add support for vscsi Olaf Hering
2015-03-02 14:20 ` Olaf Hering
2015-03-02 14:31 ` Ian Campbell
2015-03-02 15:11 ` Olaf Hering
2015-03-02 14:27 ` Olaf Hering
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=20150302182414.GA16226@aepfle.de \
--to=olaf@aepfle.de \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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.