From: Roger Pau Monne <roger.pau@entel.upc.edu>
To: xen-devel@lists.xensource.com
Subject: [PATCH 00 of 13 RFC] libxl: add hotplug script calling
Date: Wed, 18 Jan 2012 10:58:05 +0100 [thread overview]
Message-ID: <patchbomb.1326880685@loki.upc.es> (raw)
This series is a WIP, and I'm posting it now that it has reached a
state where hotplug scripts are called directly from libxl from both
Linux and NetBSD. The series has been tested with Debian stable and
NetBSD current. This is not intented to be commited to the repository,
mainly because it breaks xend by disabling udev rules on Linux. Also,
this should be applied on top of my previous patches:
libxl: fix parse_backend_path and device_backend_path to be mutual
libxl: Atomicaly check backend state and set it to 5 at device_remove
qemu: react to XenbusStateClosing
Having that said, I have in mind to move this into a separate daemon,
just like xenbackendd, but instead of listening to
/local/domain/<domid>/backend/ for changes the daemon should listen to
/hotplug/<domid>/. Then when the Dom0 request the addition of a
device (by writting the necessary entries to /hotplug/<domid>/), the
daemon should call libxl_device_*_add(...) and the same when the
device is removed (I think you can get the idea).
It would be nice if someone could take a look at this while I work on
the rest of the series, since I think that this *could* be a separate
series if it didn't break xend compatibility. In fact it will be nice
to split driver domains into two separate series, one that adds
hotplug script calling to libxl (the former), and the other one that
moves the device hotplug into a separate daemon, this will probably be
less painful than reviewing all at once.
next reply other threads:[~2012-01-18 9:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 9:58 Roger Pau Monne [this message]
2012-01-18 9:58 ` [PATCH 01 of 13 RFC] hotplug/block: get the type of block device from file path (NetBSD) Roger Pau Monne
2012-01-18 9:58 ` [PATCH 02 of 13 RFC] libxl: allow libxl__exec to take a parameter containing the env variables Roger Pau Monne
2012-01-18 9:58 ` [PATCH 03 of 13 RFC] libxl: add libxl__forkexec function to libxl_exec Roger Pau Monne
2012-01-18 9:58 ` [PATCH 04 of 13 RFC] libxl: wait for devices to initialize upon addition to the domain Roger Pau Monne
2012-01-18 9:58 ` [PATCH 05 of 13 RFC] hotplug NetBSD: pass an action instead of a state to hotplug scripts Roger Pau Monne
2012-01-18 9:58 ` [PATCH 06 of 13 RFC] libxl: perform xenstore device cleanup from libxl Roger Pau Monne
2012-01-18 9:58 ` [PATCH 07 of 13 RFC] libxl: remove force parameter from libxl__device_remove Roger Pau Monne
2012-01-18 9:58 ` [PATCH 08 of 13 RFC] libxl: add better error checking on libxl__device_remove Roger Pau Monne
2012-01-18 9:58 ` [PATCH 09 of 13 RFC] libxl: destroy devices before device model Roger Pau Monne
2012-01-26 17:23 ` Stefano Stabellini
2012-01-26 18:46 ` Roger Pau Monné
2012-01-27 10:21 ` Roger Pau Monné
2012-01-18 9:58 ` [PATCH 10 of 13 RFC] libxl: execute hotplug scripts directly from libxl Roger Pau Monne
2012-01-18 9:58 ` [PATCH 11 of 13 RFC] libxl: add hotplug script calling for NetBSD Roger Pau Monne
2012-01-18 9:58 ` [PATCH 12 of 13 RFC] libxl: add hotplug script calls for Linux Roger Pau Monne
2012-01-18 9:58 ` [PATCH 13 of 13 RFC] rc.d NetBSD: don't start xenbackendd by default, only when xend needs it Roger Pau Monne
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=patchbomb.1326880685@loki.upc.es \
--to=roger.pau@entel.upc.edu \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).