[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [PATCH 0/6] PM extension to domU

  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Wed, 7 Feb 2007 09:25:20 +0800
  • Delivery-date: Tue, 06 Feb 2007 17:25:43 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdJxpGp/qx+TgWOS6iQUGwbfBu5mQAcYarIAAczzZA=
  • Thread-topic: [Xen-devel] [PATCH 0/6] PM extension to domU

>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>Sent: 2007年2月7日 5:45
>On 6/2/07 08:12, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:
>> For the new added commands "sleep/wake", I'm not sure whether
>> it's preferred way. Since it's purpose is very simple by sending suspend
>> notification to domU, I choose to add instead of intervening complex
>> logic of save/restore. Anyway, their names do explain different
>> indeed.
>> Verified on Cset 13803.
>Have you considered destroying and recreating driver domains rather
>sleeping them? They are stateless after all, and should be quick (enough)

Sorry that I don't quite understand you. For suspend-to-disk, maybe 
we can use that policy to recreate driver domains. But for 
suspend-to-ram, that process is still slow and we just need suspend 
domain itself. Also I'm not sure why it's stateless... How do you 
recover workloads after re-creation?

>We want to support driver domain restart anyway for driver-bug isolation.
>The question mark there is whether we have the xenbus protocol sorted
>yet to allow frontends to automatically reconnect. You don't even have to
>worry about that if you're prepared to do lightweight suspend/resume of
>non-driver domains across S3.
> -- Keir

Anyway driver domain restart should be another issue. BTW, I can 
destroy and re-create a driver domain manually now. 

So, could you be more specific which part you'd like to change in 
my patch sets? :-)


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.