From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Design question for PV superpage support Date: Mon, 02 Mar 2009 17:37:26 -0800 Message-ID: <49AC89D6.7020701@goop.org> References: <200903020754.23534.dcm@mccr.org> <200903021200.09999.dcm@mccr.org> <49AC220E.9030000@Sun.COM> <200903021314.34075.dcm@mccr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200903021314.34075.dcm@mccr.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dave McCracken Cc: Xen Developers List , Mick.Jordan@sun.com List-Id: xen-devel@lists.xenproject.org Dave McCracken wrote: > My understanding of save/restore is that it will save your carefully selected > 2M pages, cheerfully restore them onto a random set of mfns, then expect your > guest to continue running. I haven't studied it enough to know whether your > guest at least gets a chance to intervene and fix things after the restore. Your guest would need to be in the position to allocate an extra 512 L1 pte pages to replace each shattered 2M page, which could be awkward - and wouldn't have any realistic way to continue if it fails to do so. Perhaps some kind of special pool of pages could be provided to the domain to help it satisfy its memory needs in recovering from a restore-shattered large page. J