WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Re: Getting rid of xenbus_suspend(): tpmfrontdriver impa

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Stefan Berger" <stefanb@xxxxxxxxxx>
Subject: RE: [Xen-devel] Re: Getting rid of xenbus_suspend(): tpmfrontdriver impacted?
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Mon, 6 Nov 2006 16:09:56 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Zhai, Edwin" <edwin.zhai@xxxxxxxxx>, xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 06 Nov 2006 00:11:02 -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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccBBEVyhCn6Gmz3EdutFQANk04WTAAdBHhg
Thread-topic: [Xen-devel] Re: Getting rid of xenbus_suspend(): tpmfrontdriver impacted?
From: Keir Fraser
Sent: 2006年11月6日 2:00

        > bit cheesy as far as I can see, so something more integrated in the 
        > tpmfront/back protocol would be nice. 

        In terms of time needed for migration there won't be a difference. Is 
supporting that .suspend really so problematic? 

        Well, we are going to handle save/restore and migration failure by 
continuing execution of the original domain. In this case xenbus_resume() will 
not be executed, so tpmfront will (I think) hang.

        I suppose we could keep suspend() and also introduce a 
suspend_cancelled() hook...

         -- Keir

When you said "xenbus_resume" will not be executed, could I suppose that only 
per-PV drivers' resume handler won't be invoked, while instead xb_init_comms 
and 
xs_resume are still invoked just after resuming point? In any case, we still 
need
rebuild xenbus channel first, and then to let PV drivers detecting re-connect, 
am I
right?

Thanks,
Kevin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel