From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: Re: [PATCH] Xen Guest Kexec Date: Mon, 27 Feb 2006 16:39:48 +0100 Message-ID: <44031D44.9010606@suse.de> References: <200507071816.28830.mark.williamson@cl.cam.ac.uk> <200602231449.52242.mark.williamson@cl.cam.ac.uk> <43FF19C3.2070409@suse.de> <200602271429.11577.mark.williamson@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: <200602271429.11577.mark.williamson@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: Mark Williamson Cc: xen-devel@lists.xensource.com, Horms List-Id: xen-devel@lists.xenproject.org > When I was looking at this approach I was intending to retreive the pageframe > info from Xen and just run unpin on anything pinned, according to its type. Is that possible? As far I know the frametable where that info is stored isn't readable by domains ... > A really big chunk of the generic kexec code is there to make sure the new > kernel is not loaded in an area that conflicts with its destination, much of > the trampoline is there to enable the new kernel to be copied on top of the > old one. Address conflicts should only be an issue if you want the second > kernel to be a dump kernel, in which case it needs to run in-place after > loading. Yep, sure, all the trampoline stuff is effectively for that. Retested, works. Not sure what I did wrong last time ... cheers, Gerd -- Gerd 'just married' Hoffmann I'm the hacker formerly known as Gerd Knorr. http://www.suse.de/~kraxel/just-married.jpeg