From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: guest kexec / domU boot loader Date: Wed, 15 Mar 2006 13:18:08 +0100 Message-ID: <44180600.3050702@suse.de> References: <44115A90.2050303@suse.de> <7ab24978871318ae238e7e362c861706@cl.cam.ac.uk> <4417FD30.6020802@suse.de> <57d91c86abbc293b0e87df1fd9cb23b1@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <57d91c86abbc293b0e87df1fd9cb23b1@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Xen devel list List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > > On 15 Mar 2006, at 11:40, Gerd Hoffmann wrote: > > You end up with a hole there. Can be filled with MEMOP_populate_physmap > if you wish. The console and xenstore pages cannot currently be moved, > but I can add support. Since the only handle the guest has on those is > their current gpfn, and Xen doesn't know about their special status, the > best approach is probably to add another 'source space' to the > MEMOP_add_to_physmap call, effectively allowing you to move a memory > page from one gpfn to another by specifying the source and target gpfns. > > Sound good? Yep, sounds good. Can XENMEM_translate_gpfn_list be used to figure where holes in the physmap (due to ballooning for example) are? Guess I can "plug" these holes then by moving around pages using the new source space? cheers, Gerd -- Gerd 'just married' Hoffmann I'm the hacker formerly known as Gerd Knorr. http://www.suse.de/~kraxel/just-married.jpeg