Re: [Xen-devel] FE driver and log dirty

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 14/7/08 08:18, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> **There must be some CPU issued accesses to target data page
> before xen_suspend is invoked, if that page is serviced by BE driver
> and has been dequeued from FE queues within the loop copy
> process. Or else log dirty mode is not triggered to re-transimit that
> page in next loop. **
> 
> Does that assumption always hold true for existing FE drivers?

Not sure what you mean? There can be requests which the FE re-queues after
resume which have in fact already been satisfied (pre-suspend) and even the
response queued up in the old shared request/response ring. The key is that
replaying them is idempotent.

 -- Keir



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