All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@citrix.com
Subject: [PATCH 0 of 3] libxl: domain shutdown cleanup
Date: Tue, 13 Dec 2011 16:24:28 +0000	[thread overview]
Message-ID: <patchbomb.1323793468@cosworth.uk.xensource.com> (raw)

The existing libxl_domain_shutdown is a bit odd, it takes an integer
"req" which can be used to indicate one of:
  * [0] = "poweroff",
  * [1] = "reboot",
  * [2] = "suspend",
  * [3] = "crash",
  * [4] = "halt",

"suspend" is not usable via this interface since it requires other
scaffolding, libxl_domain_suspend provides this already.

"halt" is the same as "poweroff".

"crash" is unused and at least Linux does not implement it. If a user
steps forward then libxl_domain_crash is trivial to add.

Therefore split libxl_domain_shutdown into libxl_domain_shutdown and
libxl_domain_reboot corresponding to "poweroff" and "reboot"
respectively.

Also push responsibility for dealing with lack of PV drivers into the
caller and at the same time improve the error messages presented to
the user when they try and "xl shutdown/reboot" an HVM guest with no
PV drivers and the corresponding documentation.

             reply	other threads:[~2011-12-13 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 16:24 Ian Campbell [this message]
2011-12-13 16:24 ` [PATCH 1 of 3] libxl: add libxl__domain_pvcontrol_{available, read, write} Ian Campbell
2011-12-13 16:24 ` [PATCH 2 of 3] libxl: split libxl_domain_shutdown into libxl_domain_shutdown & libxl_domain_reboot Ian Campbell
2011-12-13 17:11   ` Ian Campbell
2011-12-13 17:18     ` Ian Campbell
2011-12-15 17:05       ` Ian Jackson
2011-12-15 17:23         ` Ian Campbell
2011-12-13 16:24 ` [PATCH 3 of 3] libxl: report failure to reboot/shutdown due to lackof PV interfaces to caller 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=patchbomb.1323793468@cosworth.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@citrix.com \
    --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 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.