This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [PATCH] Additional states for Xenbus: Suspend/Resume

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] Additional states for Xenbus: Suspend/Resume
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Fri, 06 Jan 2006 16:37:01 -0500
Delivery-date: Fri, 06 Jan 2006 21:43:06 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

I have previously posted a version of this patch. The problem that I
have encountered with driver backends was that they were unaware of the
reason why a frontend was disappearing or why it was created. The
following patch allows the backend to see whether a frontend is going
into suspend mode and disappearing or being created due to a resume. I
have separated out the code that actually uses this awareness in the TPM
driver for another patch. Comments?

Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>

Attachment: xenbus-suspend.diff
Description: Text Data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] Additional states for Xenbus: Suspend/Resume, Stefan Berger <=