All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Marek Marczykowski <marmarek@invisiblethingslab.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: libxl: hotplug scripts and backend_domid != 0
Date: Wed, 10 Apr 2013 13:22:30 +0200	[thread overview]
Message-ID: <51654B76.8020606@citrix.com> (raw)
In-Reply-To: <1365592473.26448.31.camel@zakaz.uk.xensource.com>

On 10/04/13 13:14, Ian Campbell wrote:
> On Thu, 2013-04-04 at 16:45 +0100, Marek Marczykowski wrote:
>> Hi,
>>
>> Currently when using backend outside of dom0 (for at least one device) libxl
>> force udev call method of hotplug scripts for entire system.
> 
> Roger, do you remember why? Was it just because this change was
> relatively late in the 4.2 cycle and we were being conservative?
> 
>>  Maybe this can be
>> changed to:
>> a) if backend_domid==0, proceed according to run_hotplug_scipts
>> b) if backend_domid!=0, ignore run_hotplug_scipts and always use udev
>> ?
>>
>> Does it sound sensible?
> 
> It does, although we are now relatively late in the 4.3 cycle so I'm not
> sure it would be appropriate. George?
> 
> I think Roger is intending to implement a new scheme for driver domains
> etc in 4.4, which may make this particular issue disappear anyway.

Since run_hotplug_scripts is a global variable, not per-device, changing
it when backend_domid != 0 for a certain device might cause trouble to
other devices, or guests launched concurrently. Also udev scripts check
run_hotplug_scripts in xenstore, so changing it while there are guests
being created or destroyed might also cause trouble.

  reply	other threads:[~2013-04-10 11:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 15:45 libxl: hotplug scripts and backend_domid != 0 Marek Marczykowski
2013-04-10 11:14 ` Ian Campbell
2013-04-10 11:22   ` Roger Pau Monné [this message]
2013-04-10 11:36     ` Marek Marczykowski

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=51654B76.8020606@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=marmarek@invisiblethingslab.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.