Hello Alex.
Currently the area of dom0kernel and initrd aren't freed after they are
copied into dom0 speudo physical address space.
Would it become easier to free those area with this patch?

Thanks.

On Fri, Jun 09, 2006 at 12:28:24AM -0600, Alex Williamson wrote:
> Hi,
> 
>    I've been re-working the early start_kernel() section of xensetup.c
> to work better with the newer upstream efi changes required to boot on
> Kouya's PRIMEQUEST system.  The main problem is the ordering of calling
> reserve_memory() versus setting up the xenheap area and moving the dom0
> kernel image and ramdisk.  We also need to make sure the xenheap area is
> in a type EFI_LOADER_DATA descriptor to prevent the efi code from using
> it to store the kernel copy of the MDT.  The attached patch addresses
> these issues.  Not shown is a trivial addition to efi.c called
> efi_get_md() which returns a memory descriptor covering a given address.
> 
>    One notable difference between this code and what's currently in the
> tree is that the dom0 and initrd images are only moved if they overlap
> with the xenheap area.  The overlap should be rare, but I have hacked a
> version of elilo for testing.  I'm not sure why we unconditionally moved
> these before.  I'd appreciate any comments or feedback.  Thanks,
> 
>       Alex
> 
> -- 
> Alex Williamson                             HP Open Source & Linux Org.


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

-- 
yamahata

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

Reply via email to