Tim/Keir,
thanks for your save/restore clean up. i still have concerns about following 
changeset:
13527 -- [HVM] Save/restore cleanups 01: PIT Define public structure for the 
saved PIT data and use it instead of a series of explicit loads and stores.
if i'm right, all hw status are organized into a single & aligned struct for 
save/restore. it's clean and simple solution, but
1. it put more responsibility on developer to maintain the format/alignment of 
hw status struct.
2. compatibility issue. e.g. adding a new field in middle of the hw struct 
would 
break restoring an old image. if handling save/restore at fields granularity, 
we 
are likely to successfully restore it with only issue of this field. end user 
would be really frustrated if saved image on 3.0.4 can't be restored on 3.0.5:-(
any ideas for this?
thanks,
-- 
best rgds,
edwin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel