All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <ian.campbell@citrix.com>
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: Fri, 27 Mar 2015 08:38:34 +0100	[thread overview]
Message-ID: <20150327073834.GA12756@aepfle.de> (raw)
In-Reply-To: <1427377615.13935.59.camel@citrix.com>

On Thu, Mar 26, Ian Campbell wrote:

> On Thu, 2015-03-26 at 13:55 +0100, Olaf Hering wrote:
> > On Fri, Mar 13, Ian Campbell wrote:
> > > Also, should this be a defbool or not?
> > This is a good idea. I remmeber xend had code to make sure that all
> > devices within a vhost had the same value for "feature-host". I think
> > the intention was that whole physical hosts are passed to a domU. A
> > defbool makes it easier to preserve the initial value based on the first
> > config item.
> 
> In which case it sounds to me like this flag should be at a per-vhost
> level and not at a per device level.

Its per vhost already, "libxl_device_vscsi" refers to the virtual scsi
host, and "libxl_vscsi_dev" refers to a device connected to that host.
Perhaps the latter needs a better name to make the difference more
obvious.

Olaf

  reply	other threads:[~2015-03-27  7:38 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
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 [this message]
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=20150327073834.GA12756@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --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.