[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 0/6] PM extension to domU
On 7/2/07 01:25, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote: >> Have you considered destroying and recreating driver domains rather >> than >> sleeping them? They are stateless after all, and should be quick (enough) >> to >> boot. > > 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? A proper driver domain would be little more than a device driver wrapped in minios-style Xen-interfacing code. They should be quick to start, and restart would lose no workload. I suppose there are people running device drivers as part of a full guest however... Is it necessary to sleep/wake non driver domains? Could we check in S3 support that would work for systems with all drivers in dom0, and then consider this patchset as an extension? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |