RE: [Xen-devel] Ehancement to domU suspend/resume

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>Sent: 2007年1月18日 15:51
>
>Well, let's see what latency it adds in practise. I believe the kernel guys
>are going to use the process refrigerator for CPU hotplug so we may
>have to
>go this route anyway long term.
>
>One fear I have is that user processes doing xenbus transactions may
>be
>unable to enter the fridge if they are waiting for the transaction mutex
>(which is locked out across save/restore
>xenbus_suspend()/xenbus_resume()).
>
> -- Keir

I think that should be OK, since process freezes happen before device 
related suspend, including xenbus_suspend. System is in a 
fully-working state along with the freeze process, except that SMP has 
been hot-removed to be UP. :-)

BTW, I have a small question for the front-end driver. If there's pending 
requests within shared ring buffer at suspend, what will happen when 
FE detects connection broken after resuming back? Will those requests 
be abandoned, or continue to service after re-connected? I'm afraid that 
previous grant entries may lose after gnttab_resume...

Thanks,
Kevin

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