|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] [patch 4/4] kexec: dont initialise regions in reserve_memory
There is no need to initialise efi_memmap_res and boot_param_res in
reserve_memory() for the initial xen domain as it is done in
machine_kexec_setup_resources() using values from the kexec hypercall.
Signed-off-by: Simon Horman <horms@xxxxxxxxxxxx>
---
arch/ia64/kernel/setup.c | 15 ++++++---------
1 file changed, 6 insertions(+), 9 deletions(-)
Index: linux-2.6.18-xen.hg/arch/ia64/kernel/setup.c
===================================================================
--- linux-2.6.18-xen.hg.orig/arch/ia64/kernel/setup.c 2008-02-26
18:26:48.000000000 +0900
+++ linux-2.6.18-xen.hg/arch/ia64/kernel/setup.c 2008-02-26
18:33:54.000000000 +0900
@@ -336,15 +336,15 @@ reserve_memory (void)
}
}
}
-#ifdef CONFIG_XEN
- }
-#endif
efi_memmap_res.start = ia64_boot_param->efi_memmap;
efi_memmap_res.end = efi_memmap_res.start +
ia64_boot_param->efi_memmap_size;
boot_param_res.start = kexec_virt_to_phys(ia64_boot_param);
boot_param_res.end = boot_param_res.start +
sizeof(*ia64_boot_param);
+#ifdef CONFIG_XEN
+ }
+#endif
}
#endif
/* end of memory marker */
--
--
Horms
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|