xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Roger Pau Monne <roger.pau@citrix.com>
To: xen-devel@lists.xen.org
Subject: [PATCH v3 0/10] execute hotplug scripts from libxl
Date: Thu, 24 May 2012 09:51:56 +0100	[thread overview]
Message-ID: <1337849526-8987-1-git-send-email-roger.pau@citrix.com> (raw)

This series have been splitted in several patches, to make them easier 
to review. Also the amount of changes introduced is quite important, 
since apart from all the hotplug necessary functions and 
modifications, libxl_domain_destroy has been converted to an async op. 
This was necessary in order to have async operations during device 
removal.

Also, as an important change, disk and nics are added at different 
points for HVM and device model based guests, since we need the disk 
in order to start Qemu, but the nic hotplug scripts should be called 
at a later point, when Qemu has created the corresponding tap device.

Patches 1-4 from the previous series are already commited, so they are 
removed from v3.

Pending:

[PATCH v3 01/10] libxl: change libxl__ao_device_remove to
[PATCH v3 02/10] libxl: move device model creation prototypes
[PATCH v3 03/10] libxl: convert libxl_domain_destroy to an async op
[PATCH v3 04/10] libxl: convert libxl_device_disk_add to an asyn op
[PATCH v3 05/10] libxl: convert libxl_device_nic_add to an async
[PATCH v3 06/10] libxl: add option to choose who executes hotplug
[PATCH v3 07/10] libxl: set nic type to VIF by default
[PATCH v3 08/10] libxl: call hotplug scripts for disk devices from
[PATCH v3 09/10] libxl: call hotplug scripts for nic devices from
[PATCH v3 10/10] libxl: use libxl__xs_path_cleanup on device_destroy

Changes since v2:

 * Fixed IanJ comments.

Changes since v1:

 * Removed all the unecessary code motion and code cleanup

 * Split "convert libxl_domain_destroy to an async op" into two 
   separate patches.

             reply	other threads:[~2012-05-24  8:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  8:51 Roger Pau Monne [this message]
2012-05-24  8:51 ` [PATCH v3 01/10] libxl: change libxl__ao_device_remove to libxl__ao_device Roger Pau Monne
2012-05-24  8:51 ` [PATCH v3 02/10] libxl: move device model creation prototypes Roger Pau Monne
2012-05-24  8:51 ` [PATCH v3 03/10] libxl: convert libxl_domain_destroy to an async op Roger Pau Monne
2012-05-24  8:52 ` [PATCH v3 04/10] libxl: convert libxl_device_disk_add to an asyn op Roger Pau Monne
2012-05-24  8:52 ` [PATCH v3 05/10] libxl: convert libxl_device_nic_add to an async operation Roger Pau Monne
2012-05-24  8:52 ` [PATCH v3 06/10] libxl: add option to choose who executes hotplug scripts Roger Pau Monne
2012-05-24  8:52 ` [PATCH v3 07/10] libxl: set nic type to VIF by default Roger Pau Monne
2012-05-24  8:52 ` [PATCH v3 08/10] libxl: call hotplug scripts for disk devices from libxl Roger Pau Monne
2012-05-24  8:52 ` [PATCH v3 09/10] libxl: call hotplug scripts for nic " Roger Pau Monne
2012-05-24  8:52 ` [PATCH v3 10/10] libxl: use libxl__xs_path_cleanup on device_destroy 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=1337849526-8987-1-git-send-email-roger.pau@citrix.com \
    --to=roger.pau@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 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).