From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 4 of 9] libxl: should consider shutdown_reason for dying as well as shutdown domains
Date: Mon, 26 Jul 2010 11:56:48 +0100 [thread overview]
Message-ID: <982bf44850029802b739.1280141808@localhost.localdomain> (raw)
In-Reply-To: <patchbomb.1280141804@localhost.localdomain>
# HG changeset patch
# User Ian Campbell <ian.campbell@citrix.com>
# Date 1280140563 -3600
# Node ID 982bf44850029802b7395a03659bf440d191be2f
# Parent 1e0b63948031587b958ea307410d19c7b2be9614
libxl: should consider shutdown_reason for dying as well as shutdown domains.
A dying domain is one which has notified the hypervisor (with
SCHEDOP_shutdown) and provided a reason code but which hasn't actually
shutdown yet.
Therefore a domain which is dying will always have a valid
shutdown_reason and therefore we should obey it.
Failure to do so means there is a race between domain cleanup in the
hypervisor and the toolstack notification which can mean we may
destroy a domain which actually wanted to be rebooted.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
diff -r 1e0b63948031 -r 982bf4485002 tools/libxl/libxl.c
--- a/tools/libxl/libxl.c Mon Jul 26 11:36:02 2010 +0100
+++ b/tools/libxl/libxl.c Mon Jul 26 11:36:03 2010 +0100
@@ -416,7 +416,7 @@ static void xcinfo2xlinfo(const xc_domai
xlinfo->crashed = 0;
xlinfo->shutdown_reason = -1;
- if (xlinfo->shutdown) {
+ if (xlinfo->dying || xlinfo->shutdown) {
switch ((xcinfo->flags>>XEN_DOMINF_shutdownshift) & XEN_DOMINF_shutdownmask) {
case SHUTDOWN_poweroff:
xlinfo->shutdown_reason = LIBXL_SHUTDOWN_POWEROFF;
@@ -429,7 +429,7 @@ static void xcinfo2xlinfo(const xc_domai
break;
case SHUTDOWN_crash:
xlinfo->shutdown_reason = LIBXL_SHUTDOWN_CRASH;
- xlinfo->shutdown = 0;
+ xlinfo->shutdown = xlinfo->dying = 0;
xlinfo->crashed = 1;
break;
case SHUTDOWN_watchdog:
next prev parent reply other threads:[~2010-07-26 10:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 10:56 [PATCH 0 of 9] xl: handle domain shutdown/reboot/crash in a user configurable way Ian Campbell
2010-07-26 10:56 ` [PATCH 1 of 9] libxl: Add LIBXL_EVENT namespace to enum libxl_event_type Ian Campbell
2010-07-26 10:56 ` [PATCH 2 of 9] libxl: return libxl_dominfo from libxl_event_get_domain_death_info Ian Campbell
2010-07-26 14:32 ` Stefano Stabellini
2010-07-26 14:38 ` Ian Campbell
2010-07-26 14:59 ` Stefano Stabellini
2010-07-26 15:26 ` Ian Jackson
2010-07-26 15:31 ` Ian Campbell
2010-07-26 15:36 ` Ian Jackson
2010-07-26 15:34 ` Stefano Stabellini
2010-07-26 15:41 ` Ian Jackson
2010-07-26 16:23 ` Stefano Stabellini
2010-07-26 16:38 ` Ian Jackson
2010-07-27 9:22 ` Ian Campbell
2010-07-27 9:53 ` Stefano Stabellini
2010-07-26 10:56 ` [PATCH 3 of 9] libxl: signal caller if domain already destroyed on domain death event Ian Campbell
2010-07-26 14:32 ` Stefano Stabellini
2010-07-26 14:41 ` Ian Campbell
2010-07-26 14:58 ` Stefano Stabellini
2010-07-26 15:02 ` Ian Campbell
2010-07-26 15:08 ` Stefano Stabellini
2010-07-26 10:56 ` Ian Campbell [this message]
2010-07-26 10:56 ` [PATCH 5 of 9] libxl: add libxl_domain_preserve Ian Campbell
2010-07-26 15:30 ` Ian Jackson
2010-07-26 15:56 ` Ian Campbell
2010-07-26 10:56 ` [PATCH 6 of 9] xl: do not try and auto re-connect console on reboot Ian Campbell
2010-07-26 10:56 ` [PATCH 7 of 9] xl: Add function to generate random uuid and use it Ian Campbell
2010-07-26 10:56 ` [PATCH 8 of 9] xl: Factor out domain death handling into a separate function Ian Campbell
2010-07-26 10:56 ` [PATCH 9 of 9] xl: support on_{poweroff, reboot, crash} domain configuration options 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=982bf44850029802b739.1280141808@localhost.localdomain \
--to=ian.campbell@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 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).