From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aurelien Chartier Subject: [PATCH 0/2] xenbus: Fix S3 frontend resume when xenstored is not running Date: Wed, 1 May 2013 13:57:20 +0100 Message-ID: <1367413042-13987-1-git-send-email-aurelien.chartier@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xensource.com Cc: Aurelien Chartier , stefano.stabellini@eu.citrix.com, ian.campbell@citrix.com, JBeulich@suse.com, konrad.wilk@oracle.com List-Id: xen-devel@lists.xenproject.org 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(-)