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] [Linux] [TPM driver] Resume frontend after checkpoin

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] [Linux] [TPM driver] Resume frontend after checkpointing
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Thu, 01 Mar 2007 10:22:18 -0500
Cc: keir@xxxxxxxxxxxxx
Delivery-date: Thu, 01 Mar 2007 07:24:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Reply-to: stefanb@xxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
This patch implements TPM frontend driver resume after checkpointing a
I also now let the front-end wait for the response from the TPM until
the response is there. A response must come due to the strict request /
response nature of the protocol, but the time until the responses
arrives depends on the type of operation that is executed by the vTPM.
Resending a request is not possible with this type of device.

I tested this patch with the vTPM-relevant tests in the xm-test suite.

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

Attachment: tpmfront_suspend_cancel.diff
Description: Text Data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] [Linux] [TPM driver] Resume frontend after checkpointing, Stefan Berger <=