On 6/14/11 1:20 PM, "Schuh, Richard" <rsc...@visa.com> wrote:
>An absolute prereq, not just a safety one. If it is not already draining, >then there would be nothing to prevent new pages from being written on >the device. Yeah. Playing with it on the whiteboard indicated that. Probably the only safe way to get a CP interlock in place that would prevent new pages being written. >It will still be somewhat tricky because the page may already be in >storage, in use by a virtual machine. Also, it may be part of a DCSS, in >which case, only your private copy (resulting from your changing the >page) will be paged out by your activity; others will still be >referencing the original page. I think that's why you'd have to force CP to dirty the page rather than doing it inside a virtual machine, especially with CP's own pages potentially written at startup. Probably only doable from inside CP itself, or at minimum, via manipulate of real storage rather than virtual storage. There Be Dragons. Another project for my Copious Spare Time. Not. -- db >>
