This patch adds the BSS to the resource tree just as kernel text and kernel

data are in the resource tree. The main reason behind this is to avoid

crashkernel reservation in that area.
Signed-off-by: Bernhard Walle <bwalle@suse.de>
---

 arch/x86/kernel/e820_32.c  |    8 ++++++++

 arch/x86/kernel/e820_64.c  |    3 ++-

 arch/x86/kernel/efi_32.c   |    3 +++

 arch/x86/kernel/setup_32.c |    4 ++++

 arch/x86/kernel/setup_64.c |    9 +++++++++

 5 files changed, 26 insertions(+), 1 deletion(-)
--- a/arch/x86/kernel/e820_32.c

+++ b/arch/x86/kernel/e820_32.c

@@ -51,6 +51,13 @@ struct resource code_resource = {

 	.flags	= IORESOURCE_BUSY | IORESOURCE_MEM

 };
+struct resource bss_resource = {

+	.name	= "Kernel bss",

+	.start	= 0,

+	.end	= 0,

+	.flags	= IORESOURCE_BUSY | IORESOURCE_MEM

+};

+

 static struct resource system_rom_resource = {

 	.name	= "System ROM",

 	.start	= 0xf0000,

@@ -287,6 +294,7 @@ legacy_init_iomem_resources(struct resou

 			 */

 			request_resource(res, code_resource);

 			request_resource(res, data_resource);

+			request_resource(res, &bss_resource);

 #ifdef CONFIG_KEXEC

 			if (crashk_res.start != crashk_res.end)

 				request_resource(res, &crashk_res);

--- a/arch/x86/kernel/e820_64.c

+++ b/arch/x86/kernel/e820_64.c

@@ -47,7 +47,7 @@ unsigned long end_pfn_map;

  */

 static unsigned long __initdata end_user_pfn = MAXMEM>>PAGE_SHIFT;
-extern struct resource code_resource, data_resource;

+extern struct resource code_resource, data_resource, bss_resource;
 /* Check for some hardcoded bad areas that early boot is not allowed to touch */

 static inline int bad_addr(unsigned long *addrp, unsigned long size)

@@ -220,6 +220,7 @@ void __init e820_reserve_resources(void)

 			 */

 			request_resource(res, &code_resource);

 			request_resource(res, &data_resource);

+			request_resource(res, &bss_resource);

 #ifdef CONFIG_KEXEC

 			if (crashk_res.start != crashk_res.end)

 				request_resource(res, &crashk_res);...
[ message continues ]

On Mon, 15 Oct 2007 13:50:43 +0200
Looks ungainly, doesn't it?  Perhaps we should add a third arg to

legacy_init_iomem_resources(), or change legacy_init_iomem_resources() to

take zero args?

-

Yes. But when we change legacy_init_iomem_resources(), then we should

also change efi_initialize_iomem_resources(). But that's declared in

<linux/efi.h> and so a change in ia64 code is required which I wanted

to avoid.
But that patch is for review of the idea. If nobody has objections,

then I'll implement the IA64 change anyway -- and then the 3rd

parameter can be added.
Thanks,

   Bernhard

-