All of lore.kernel.org
 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>,
	stefano.stabellini@eu.citrix.com, ian.campbell@citrix.com,
	JBeulich@suse.com, konrad.wilk@oracle.com
Subject: [PATCH 0/2] xenbus: Fix S3 frontend resume when xenstored is not running
Date: Wed, 1 May 2013 13:57:20 +0100	[thread overview]
Message-ID: <1367413042-13987-1-git-send-email-aurelien.chartier@citrix.com> (raw)

Hi,

This patch series fixes the S3 resume of dom0 or a Xenstore stub domain
running 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 bypassing the xenbus frontend
resume when we are running in dom0 or a Xenstore stub domain.

Aurelien Chartier (2):
  xenbus: save xenstore local status for later use
  xenbus: bypass 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 |   15 ++++++++++++++-
 4 files changed, 34 insertions(+), 16 deletions(-)

             reply	other threads:[~2013-05-01 12:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 12:57 Aurelien Chartier [this message]
2013-05-01 12:57 ` [PATCH 1/2] xenbus: save xenstore local status for later use Aurelien Chartier
2013-05-01 12:57 ` [PATCH 2/2] xenbus: bypass xenbus frontend resume if xenstored is not running Aurelien Chartier
2013-05-02  8:24   ` Ian Campbell
2013-05-02  9:21     ` Jan Beulich
2013-05-02  9:24       ` Ian Campbell
2013-05-02 10:10         ` Aurélien Chartier
2013-05-02 10:30           ` Ian Campbell
2013-05-02 12:32             ` 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=1367413042-13987-1-git-send-email-aurelien.chartier@citrix.com \
    --to=aurelien.chartier@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@eu.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.