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

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

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Tue, 6 Feb 2007 16:12:41 +0800
  • Delivery-date: Tue, 06 Feb 2007 00:12:46 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdJxpGp/qx+TgWOS6iQUGwbfBu5mQ==
  • Thread-topic: [PATCH 0/6] PM extension to domU

Hi, all,
        Current domU suspend/resume infrastructure doesn't satisfy 
physical PM activity like Xen S3, as I posted before:

        Basically this patch set adds two features:
                - Driver domain suspend/resume support
                - Light-weight suspend/resume, with all old domain
context kept

        For the driver domain, new added logic like process freeze is 
skipped for non-driver domain to avoid impact. One important note 
here is, driver domain suspend will only work correctly for the new 
added commands, where old domain context are still kept intact 
after resume. For save/restore and migration, there's no easy way 
to do when domain is destroyed and re-created. The reason is the 
machine address saved within private driver structures. Unless 
domainU itself takes IOMMU as the default DMA interface for all 
drivers, we may need to explicitly prevent user from 
save/restore/migration on driver domain later.

        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 meaning 

        Verified on Cset 13803.


Xen-devel mailing list



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