xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Chartier <aurelien.chartier@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Aurelien Chartier <aurelien.chartier@citrix.com>,
	konrad.wilk@oracle.com, ian.campbell@citrix.com,
	JBeulich@suse.com, david.vrabel@citrix.com
Subject: [PATCH V5 0/2] xenbus: Fix S3 frontend resume when xenstored is not running
Date: Tue, 28 May 2013 18:09:54 +0100	[thread overview]
Message-ID: <1369760996-23616-1-git-send-email-aurelien.chartier@citrix.com> (raw)

Hi,

This patch series fixes the S3 resume of a domain running xenstored and a
frontend over xenbus (xen-netfront in my use case).

As device resume is happening before process resume, the xenbus frontend
resume is hanging if xenstored is not running, thus causing a deadlock.
This patch series is fixing that issue by deferring the xenbus frontend
resume when we are running xenstored in that same domain.

Aurelien Chartier (2):
  xenbus: save xenstore local status for later use
  xenbus: delay xenbus frontend resume if xenstored is not running

 drivers/xen/xenbus/xenbus_comms.h          |    1 +
 drivers/xen/xenbus/xenbus_probe.c          |   27 +++++++++-----------
 drivers/xen/xenbus/xenbus_probe.h          |    7 ++++++
 drivers/xen/xenbus/xenbus_probe_frontend.c |   37 +++++++++++++++++++++++++++-
 include/xen/xenbus.h                       |    1 +
 5 files changed, 57 insertions(+), 16 deletions(-)

-- 
1.7.10.4

             reply	other threads:[~2013-05-28 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 17:09 Aurelien Chartier [this message]
2013-05-28 17:09 ` [PATCH V5 1/2] xenbus: save xenstore local status for later use Aurelien Chartier
2013-05-28 17:09 ` [PATCH V5 2/2] xenbus: delay xenbus frontend resume if xenstored is not running Aurelien Chartier
2013-05-29  7:03   ` Jan Beulich
2013-05-29 15:44     ` Konrad Rzeszutek Wilk
2013-05-29 16:17       ` Aurelien Chartier

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=1369760996-23616-1-git-send-email-aurelien.chartier@citrix.com \
    --to=aurelien.chartier@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=konrad.wilk@oracle.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).