From: Roger Pau Monne <roger.pau@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v3 3/5] libxl: call hotplug scripts from libxl for vbd
Date: Wed, 25 Apr 2012 14:53:14 +0100 [thread overview]
Message-ID: <4F9801CA.6040800@citrix.com> (raw)
In-Reply-To: <20374.33383.748153.64321@mariner.uk.xensource.com>
Ian Jackson escribió:
> Ian Campbell writes ("Re: [Xen-devel] [PATCH v3 3/5] libxl: call hotplug scripts from libxl for vbd"):
>> On Tue, 2012-04-24 at 11:27 +0100, Ian Jackson wrote:
>>> I was suggesting that the key should be global, and XENBUS_PATH
>>> contains too much.
>> Ah, I saw "latter" and read the last bit of my sentence "per-device", my
>> mistake.
>
> Right.
>
> The reason I think it should be global is that this is a transitional
> bodge to make driver domains continue to work pending a proper
> sorting-out in 4.3. So there is no need to make it fully general.
>
> Ian.
So the new variable should be global, even between devices, so that we
either enable hotplug script calling from xl for all, or for none.
Something like:
/libxl/run_hotplug_scripts
Thanks.
next prev parent reply other threads:[~2012-04-25 13:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 13:23 [PATCH v3 0/5] libxl: call hotplug scripts from libxl Roger Pau Monne
2012-04-20 13:23 ` [PATCH v3 1/5] libxl: allow libxl__exec to take a parameter containing the env variables Roger Pau Monne
2012-04-23 15:37 ` Ian Jackson
2012-04-20 13:23 ` [PATCH v3 2/5] libxl: add libxl__xs_path_cleanup Roger Pau Monne
2012-04-23 15:33 ` Ian Jackson
2012-04-23 15:42 ` Roger Pau Monne
2012-04-23 16:49 ` Ian Jackson
2012-04-23 16:52 ` Ian Jackson
2012-04-25 13:19 ` Roger Pau Monne
2012-05-02 9:44 ` Roger Pau Monne
2012-04-20 13:23 ` [PATCH v3 3/5] libxl: call hotplug scripts from libxl for vbd Roger Pau Monne
2012-04-23 16:48 ` Ian Jackson
2012-04-24 9:16 ` Ian Campbell
2012-04-24 10:09 ` Ian Jackson
2012-04-24 10:17 ` Ian Campbell
2012-04-24 10:27 ` Ian Jackson
2012-04-24 10:29 ` Ian Campbell
2012-04-24 10:37 ` Ian Jackson
2012-04-25 13:53 ` Roger Pau Monne [this message]
2012-04-25 14:59 ` Ian Campbell
[not found] ` <4F982F18.2080902@citrix.com>
2012-04-26 11:48 ` Fwd: " Roger Pau Monne
2012-04-26 12:06 ` Ian Campbell
2012-04-26 12:12 ` Roger Pau Monne
2012-04-26 13:02 ` Ian Jackson
2012-04-26 13:09 ` Ian Campbell
2012-05-11 16:06 ` Ian Jackson
2012-05-11 16:26 ` Ian Campbell
2012-04-20 13:23 ` [PATCH v3 4/5] libxl: call hotplug scripts from libxl for vif Roger Pau Monne
2012-04-23 16:59 ` Ian Jackson
2012-04-24 9:18 ` Ian Campbell
2012-04-25 11:19 ` Ian Campbell
2012-04-25 11:24 ` Roger Pau Monne
2012-04-20 13:23 ` [PATCH v3 5/5] libxl: add "downscript=no" to Qemu call Roger Pau Monne
2012-04-23 15:38 ` Ian Jackson
2012-04-23 12:12 ` [PATCH v3 0/5] libxl: call hotplug scripts from libxl Marek Marczykowski
2012-04-23 13:31 ` Roger Pau Monne
2012-04-23 13:47 ` Marek Marczykowski
2012-04-23 13:59 ` Non-dom0 block backends (was: Re: [PATCH v3 0/5] libxl: call hotplug scripts from libxl) Joanna Rutkowska
2012-04-23 14:02 ` [PATCH v3 0/5] libxl: call hotplug scripts from libxl Ian Campbell
2012-04-23 16:25 ` Roger Pau Monne
2012-04-24 9:18 ` Ian Campbell
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=4F9801CA.6040800@citrix.com \
--to=roger.pau@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.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.