Skip to contentSkip to conversation

multiboot2: Add module relocatable tag to support modules relocation

PATCH In review Zide Chen 2 participants 5 messages Apr 16, 2020 – May 11, 2020

lore
Share & tools
lore

Zide Chen

author
#0 lore raw

PATCH 1/1 multiboot2: Add module relocatable tag to support modules relocation

Also change the name from "relocatable header tag" to "kernel relocatable tag" to make it less confusing. These two tags are independent from each other.

---
 doc/multiboot.texi | 51 +++++++++++++++++++++++++++++++++++++++++-----
 doc/multiboot2.h   | 11 ++++++++++
 2 files changed, 57 insertions(+), 5 deletions(-)
doc/multiboot.texi +46 -5
index df8a0d056e76..bf0150dc86a0 100644
@@ -355,7 +355,8 @@ executable header.
 * Console header tags::
 * Module alignment tag::
 * EFI boot services tag::
-* Relocatable header tag::
+* Kernel relocatable tag::
+* Module relocatable tag::
 
 @end menu
 
@@ -691,8 +692,8 @@ u32     | size = 8          |
 This tag indicates that payload supports starting without
 terminating boot services.
 
-@node Relocatable header tag
-@subsection Relocatable header tag
+@node Kernel relocatable tag
+@subsection Kernel relocatable tag
 
 @example
 @group
@@ -708,7 +709,7 @@ u32     | preference        |
 @end group
 @end example
 
-This tag indicates that image is relocatable.
+This tag indicates that kernel image is relocatable.
 
 The meaning of each field is as follows:
 
@@ -730,6 +731,46 @@ Boot loader should follow it. @samp{0} means none, @samp{1} means
 load image at lowest possible address but not lower than min_addr
 and @samp{2} means load image at highest possible address but not
 higher than max_addr.
+
+@node Module relocatable tag
+@subsection Module relocatable tag
+
+@example
+@group
+        +-------------------+
+u16     | type = 11         |
+u16     | flags             |
+u32     | size = 20         |
+u32     | min_addr          |
+u32     | max_addr          |
+u32     | preference        |
+        +-------------------+
+@end group
+@end example
+
+This tag is independent to the kernel relocatable tag. All of the
+address fields in this tag are physical addresses.
+
+The meaning of each field is as follows:
+
+@table @code
+@item min_addr
+Lowest possible physical address at which any modules should be
+loaded. The bootloader cannot load any part of any modules below
+this address.
+
+@item max_addr
+Highest possible physical address at which any loaded modules should
+end. The bootloader cannot load any part of any modules above this
+address.
+
+@item preference
+It contains load address placement suggestion for Multiboot2 modules
+Boot loader should follow it. @samp{0} means load modules not lower
+than min_addr, and not higher than max_addr, but no preference on either
+lower or higher address; @samp{1} means load modules at lowest possible
+address but not lower than min_addr; @samp{2} means load modules at
+highest possible address but not higher than max_addr.
 @end table
 
 @node Machine state
@@ -1399,7 +1440,7 @@ u32     | load_base_addr    |
 @end example
 
 This tag contains image load base physical address. It is
-provided only if image has relocatable header tag.
+provided only if image has kernel relocatable tag.
 
 @node Examples
 @chapter Examples
doc/multiboot2.h +11 -0
index b181607075b2..d97d10c2691a 100644
@@ -75,6 +75,7 @@
 #define MULTIBOOT_HEADER_TAG_ENTRY_ADDRESS_EFI32  8
 #define MULTIBOOT_HEADER_TAG_ENTRY_ADDRESS_EFI64  9
 #define MULTIBOOT_HEADER_TAG_RELOCATABLE  10
+#define MULTIBOOT_HEADER_TAG_MODULE_RELOCATABLE  11
 
 #define MULTIBOOT_ARCHITECTURE_I386  0
 #define MULTIBOOT_ARCHITECTURE_MIPS32  4
@@ -179,6 +180,16 @@ struct multiboot_header_tag_relocatable
   multiboot_uint32_t preference;
 };
 
+struct multiboot_header_tag_module_relocatable
+{
+  multiboot_uint16_t type;
+  multiboot_uint16_t flags;
+  multiboot_uint32_t size;
+  multiboot_uint32_t min_addr;
+  multiboot_uint32_t max_addr;
+  multiboot_uint32_t preference;
+};
+
 struct multiboot_color
 {
   multiboot_uint8_t red;
Signature · 1 line
2.17.1
author
#1 lore raw

PATCH 1/1 multiboot2: Implement the new module_relocatable_tag

In contrast to Mulitboot, in Mulitboot2, there is currently no way to control where to load the modules to. This could be a problem, e.g., the OS loaded by Multiboot2 needs to reserve low address for some particular purposes and not for loading modules.

This new tag gives it flexibility to control the modules load addresses, which is independent to whether the kernel relocatable tag is present or not.

---
 grub-core/loader/multiboot.c      | 22 ++++++++++++++++++++--
 grub-core/loader/multiboot_mbi2.c | 23 +++++++++++++++++++++++
 include/grub/multiboot2.h         |  9 +++++++++
 include/multiboot2.h              | 11 +++++++++++
 4 files changed, 63 insertions(+), 2 deletions(-)
grub-core/loader/multiboot.c +20 -2
index 4a98d7082598..099a8e981126 100644
@@ -369,6 +369,8 @@ grub_cmd_module (grub_command_t cmd __attribute__ ((unused)),
   grub_err_t err;
   int nounzip = 0;
   grub_uint64_t lowest_addr = 0;
+  grub_uint64_t max_addr;
+  int preference = GRUB_RELOCATOR_PREFERENCE_NONE;
 
   if (argc == 0)
     return grub_error (GRUB_ERR_BAD_ARGUMENT, N_("filename expected"));
@@ -401,11 +403,27 @@ grub_cmd_module (grub_command_t cmd __attribute__ ((unused)),
   size = grub_file_size (file);
   if (size)
   {
+    max_addr = (0xffffffff - size) + 1;
+
+#ifdef GRUB_USE_MULTIBOOT2
+    if (grub_multiboot2_mri.relocatable)
+      {
+        lowest_addr = grub_multiboot2_mri.min_addr;
+        max_addr = grub_multiboot2_mri.max_addr;
+        preference = grub_multiboot2_mri.preference;
+        if (size > max_addr || lowest_addr > max_addr - size)
+          {
+            grub_file_close (file);
+            return grub_error (GRUB_ERR_BAD_ARGUMENT, "invalid min/max address and/or load size for modules");
+          }
+      }
+#endif
+
     grub_relocator_chunk_t ch;
     err = grub_relocator_alloc_chunk_align (GRUB_MULTIBOOT (relocator), &ch,
-					    lowest_addr, (0xffffffff - size) + 1,
+					    lowest_addr, max_addr,
 					    size, MULTIBOOT_MOD_ALIGN,
-					    GRUB_RELOCATOR_PREFERENCE_NONE, 1);
+					    preference, 1);
     if (err)
       {
 	grub_file_close (file);
grub-core/loader/multiboot_mbi2.c +23 -0
index 18e766c7b31c..c2639623228e 100644
@@ -75,6 +75,7 @@ static unsigned elf_sec_shstrndx;
 static void *elf_sections;
 static int keep_bs = 0;
 static grub_uint32_t load_base_addr;
+struct module_relocatable_info grub_multiboot2_mri;
 
 void
 grub_multiboot2_add_elfsyms (grub_size_t num, grub_size_t entsize,
@@ -114,6 +115,7 @@ grub_multiboot2_load (grub_file_t file, const char *filename)
   struct multiboot_header_tag *tag;
   struct multiboot_header_tag_address *addr_tag = NULL;
   struct multiboot_header_tag_relocatable *rel_tag;
+  struct multiboot_header_tag_module_relocatable *mod_rel_tag;
   int entry_specified = 0, efi_entry_specified = 0;
   grub_addr_t entry = 0, efi_entry = 0;
   grub_uint32_t console_required = 0;
@@ -123,6 +125,7 @@ grub_multiboot2_load (grub_file_t file, const char *filename)
 
   mld.mbi_ver = 2;
   mld.relocatable = 0;
+  grub_multiboot2_mri.relocatable = 0;
 
   mld.buffer = grub_malloc (MULTIBOOT_SEARCH);
   if (!mld.buffer)
@@ -248,6 +251,26 @@ grub_multiboot2_load (grub_file_t file, const char *filename)
 	  }
 	break;
 
+      case MULTIBOOT_HEADER_TAG_MODULE_RELOCATABLE:
+	mod_rel_tag = (struct multiboot_header_tag_module_relocatable *) tag;
+	grub_multiboot2_mri.relocatable = 1;
+	grub_multiboot2_mri.min_addr = mod_rel_tag->min_addr;
+	grub_multiboot2_mri.max_addr = mod_rel_tag->max_addr;
+	switch (mod_rel_tag->preference)
+	  {
+	  case MULTIBOOT_LOAD_PREFERENCE_LOW:
+	    grub_multiboot2_mri.preference = GRUB_RELOCATOR_PREFERENCE_LOW;
+	    break;
+
+	  case MULTIBOOT_LOAD_PREFERENCE_HIGH:
+	    grub_multiboot2_mri.preference = GRUB_RELOCATOR_PREFERENCE_HIGH;
+	    break;
+
+	  default:
+	    grub_multiboot2_mri.preference = GRUB_RELOCATOR_PREFERENCE_NONE;
+	  }
+	break;
+
 	/* GRUB always page-aligns modules.  */
       case MULTIBOOT_HEADER_TAG_MODULE_ALIGN:
 	break;
include/grub/multiboot2.h +9 -0
index 502d34ef1804..6d7598eeffcc 100644
@@ -92,6 +92,14 @@ struct mbi_load_data
 };
 typedef struct mbi_load_data mbi_load_data_t;
 
+struct module_relocatable_info
+{
+  int relocatable;
+  grub_uint32_t min_addr;
+  grub_uint32_t max_addr;
+  grub_uint32_t preference;
+};
+
 /* Load ELF32 or ELF64.  */
 grub_err_t
 grub_multiboot2_load_elf (mbi_load_data_t *mld);
@@ -99,6 +107,7 @@ grub_multiboot2_load_elf (mbi_load_data_t *mld);
 extern grub_size_t grub_multiboot2_pure_size;
 extern grub_size_t grub_multiboot2_alloc_mbi;
 extern grub_uint32_t grub_multiboot2_payload_eip;
+extern struct module_relocatable_info grub_multiboot2_mri;
 
 
 #endif /* ! GRUB_MULTIBOOT_HEADER */
include/multiboot2.h +11 -0
index 5693923c014f..41b973aed193 100644
@@ -74,6 +74,7 @@
 #define MULTIBOOT_HEADER_TAG_EFI_BS  7
 #define MULTIBOOT_HEADER_TAG_ENTRY_ADDRESS_EFI64  9
 #define MULTIBOOT_HEADER_TAG_RELOCATABLE  10
+#define MULTIBOOT_HEADER_TAG_MODULE_RELOCATABLE  11
 
 #define MULTIBOOT2_ARCHITECTURE_I386  0
 #define MULTIBOOT2_ARCHITECTURE_MIPS32  4
@@ -178,6 +179,16 @@ struct multiboot_header_tag_relocatable
   multiboot_uint32_t preference;
 };
 
+struct multiboot_header_tag_module_relocatable
+{
+  multiboot_uint16_t type;
+  multiboot_uint16_t flags;
+  multiboot_uint32_t size;
+  multiboot_uint32_t min_addr;
+  multiboot_uint32_t max_addr;
+  multiboot_uint32_t preference;
+};
+
 struct multiboot_color
 {
   multiboot_uint8_t red;
Signature · 1 line
2.17.1
#2 lore raw
In reply to Zide Chen
Quoted 3 lines · Zide Chen

Also change the name from "relocatable header tag" to "kernel relocatable tag" to make it less confusing. These two tags are independent from each other.

First of all, the commit message should say what the patch does and why. Just in a few words. You do not need to repeat everything from below. Though it have to be clear what happens without looking at the patch content.

Additionally, may I ask you to send new patch for Multiboo2 spec with "[MULTIBOOT2 SPEC PATCH]" subject prefix instead of normal "[PATCH]" one?

Quoted 11 lines
---
 doc/multiboot.texi | 51 +++++++++++++++++++++++++++++++++++++++++-----
 doc/multiboot2.h   | 11 ++++++++++
 2 files changed, 57 insertions(+), 5 deletions(-)
doc/multiboot.texi +0 -0
index df8a0d056e76..bf0150dc86a0 100644

doc/multiboot.texi executable header. · line 359

Quoted 6 lines
doc/multiboot.texi +2 -1
@@ -355,7 +355,8 @@ executable header.
 * Console header tags::
 * Module alignment tag::
 * EFI boot services tag::
-* Relocatable header tag::
+* Kernel relocatable tag::
+* Module relocatable tag::

IMO this is not "Module relocatable tag". It is rather "Module load preferences tag".

doc/multiboot.texi u32 | size = 8 | · line 696

Quoted 10 lines
doc/multiboot.texi +2 -2
 @end menu
 
@@ -691,8 +692,8 @@ u32     | size = 8          |
 This tag indicates that payload supports starting without
 terminating boot services.
 
-@node Relocatable header tag
-@subsection Relocatable header tag
+@node Kernel relocatable tag
+@subsection Kernel relocatable tag

I am OK with this change. However, it should be done in separate patch.

doc/multiboot.texi u32 | preference | · line 712

Quoted 8 lines
doc/multiboot.texi +1 -1
 @example
 @group
@@ -708,7 +709,7 @@ u32     | preference        |
 @end group
 @end example
 
-This tag indicates that image is relocatable.
+This tag indicates that kernel image is relocatable.

Ditto. However, if you want to change this then whole description of relocatable header tag requires more editing too.

doc/multiboot.texi Boot loader should follow it. @samp{0} means none, @samp{1} means · line 736

Quoted 9 lines
doc/multiboot.texi +3 -0
 The meaning of each field is as follows:
 
@@ -730,6 +731,46 @@ Boot loader should follow it. @samp{0} means none, @samp{1} means
 load image at lowest possible address but not lower than min_addr
 and @samp{2} means load image at highest possible address but not
 higher than max_addr.
+
+@node Module relocatable tag
+@subsection Module relocatable tag

Please take a look above...

Quoted 21 lines
doc/multiboot.texi +21 -0
+@example
+@group
+        +-------------------+
+u16     | type = 11         |
+u16     | flags             |
+u32     | size = 20         |
+u32     | min_addr          |
+u32     | max_addr          |
+u32     | preference        |
+        +-------------------+
+@end group
+@end example
+
+This tag is independent to the kernel relocatable tag. All of the
+address fields in this tag are physical addresses.
+
+The meaning of each field is as follows:
+
+@table @code
+@item min_addr
+Lowest possible physical address at which any modules should be

doc/multiboot.texi Boot loader should follow it. @samp{0} means none, @samp{1} means · line 768

Quoted 10 lines
doc/multiboot.texi +10 -0
+loaded. The bootloader cannot load any part of any modules below
+this address.
+
+@item max_addr
+Highest possible physical address at which any loaded modules should
+end. The bootloader cannot load any part of any modules above this
+address.
+
+@item preference
+It contains load address placement suggestion for Multiboot2 modules

s/Multiboot2 modules/the boot loader./

doc/multiboot.texi Boot loader should follow it. @samp{0} means none, @samp{1} means · line 770

Quoted 2 lines
doc/multiboot.texi +2 -0
+Boot loader should follow it. @samp{0} means load modules not lower
+than min_addr, and not higher than max_addr, but no preference on either

s/,//g

doc/multiboot.texi Boot loader should follow it. @samp{0} means none, @samp{1} means · line 771

Quoted 1 line
doc/multiboot.texi +1 -0
+lower or higher address; @samp{1} means load modules at lowest possible

s/;/./

doc/multiboot.texi Boot loader should follow it. @samp{0} means none, @samp{1} means · line 772

Quoted 1 line
doc/multiboot.texi +1 -0
+address but not lower than min_addr; @samp{2} means load modules at

s/;/./

doc/multiboot.texi Boot loader should follow it. @samp{0} means none, @samp{1} means · line 773

Quoted 1 line
doc/multiboot.texi +1 -0
+highest possible address but not higher than max_addr.

After reading all threads related to this change somehow I got an impression that you want to use this tag to ask the booloader to load the modules above the kernel. Am I right? If this is true then we should have another value, 4, which says: please load modules above the kernel. ...and maybe 8 for below the kernel... Or vice versa would be better. Otherwise IMO you will be playing games with relocatable tag and this new tag to gain what you want. This will be not nice and maybe not very reliable.

Daniel

author
#3 lore raw

Hi Daniel,

Thank you very much for your review! Comments inline:

Best Regards,
Zide

Quoted 7 lines

-----Original Message-----
From: Daniel Kiper <[email protected]>
Sent: Thursday, May 7, 2020 5:54 AM
To: Chen, Zide <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] multiboot2: Add module relocatable tag to support modules relocation

Quoted 8 lines
Quoted 3 lines · Zide Chen

Also change the name from "relocatable header tag" to "kernel relocatable tag" to make it less confusing. These two tags are independent from each other.

First of all, the commit message should say what the patch does and why. Just in a few words. You do not need to repeat everything from below. Though it have to be clear what happens without looking at the patch content.

Yes, will do.

Quoted 2 lines

Additionally, may I ask you to send new patch for Multiboo2 spec with "[MULTIBOOT2 SPEC PATCH]" subject prefix instead of normal "[PATCH]" one?

Yes, will do.

Quoted 6 lines
Quoted 6 lines
---
 doc/multiboot.texi | 51 +++++++++++++++++++++++++++++++++++++++++-----
 doc/multiboot2.h   | 11 ++++++++++
 2 files changed, 57 insertions(+), 5 deletions(-)
Quoted 14 lines

doc/multiboot.texi executable header. · line 359

Quoted 11 lines
doc/multiboot.texi +2 -1
index df8a0d056e76..bf0150dc86a0 100644
@@ -355,7 +355,8 @@ executable header.
 * Console header tags::
 * Module alignment tag::
 * EFI boot services tag::
-* Relocatable header tag::
+* Kernel relocatable tag::
+* Module relocatable tag::

IMO this is not "Module relocatable tag". It is rather "Module load preferences tag".

Sure, I can change the name. I chose this name because the contain of this new tag is almost identical to the relocatable header tag.

Quoted 6 lines
Quoted 6 lines
doc/multiboot.texi +0 -0
 @end menu
 
@@ -691,8 +692,8 @@ u32     | size = 8          |
 This tag indicates that payload supports starting without
 terminating boot services.
 
Quoted 6 lines

doc/multiboot.texi u32 | size = 8 | · line 696

Quoted 4 lines
doc/multiboot.texi +2 -2
-@node Relocatable header tag
-@subsection Relocatable header tag
+@node Kernel relocatable tag
+@subsection Kernel relocatable tag

I am OK with this change. However, it should be done in separate patch.

If this new tag is not named as "module relocatable tag", then I don't think it's needed to do this name changing any more, since now these two names are not confusing any more.

Quoted 7 lines
Quoted 7 lines
doc/multiboot.texi +0 -0
 @example
 @group
@@ -708,7 +709,7 @@ u32     | preference        |
 @end group
 @end example
 
Quoted 5 lines

doc/multiboot.texi u32 | preference | · line 712

Quoted 2 lines
doc/multiboot.texi +1 -1
-This tag indicates that image is relocatable.
+This tag indicates that kernel image is relocatable.

Ditto. However, if you want to change this then whole description of relocatable header tag requires more editing too.

Ditto. Seems no need to change name for relocatable header tag any more.

Quoted 7 lines
Quoted 7 lines
doc/multiboot.texi +7 -0
+@table @code
+@item min_addr
+Lowest possible physical address at which any modules should be
+loaded. The bootloader cannot load any part of any modules below
+this address.
+
+@item max_addr
Quoted 8 lines

doc/multiboot.texi Boot loader should follow it. @samp{0} means none, @samp{1} means · line 768

Quoted 6 lines
doc/multiboot.texi +6 -0
+Highest possible physical address at which any loaded modules should
+end. The bootloader cannot load any part of any modules above this
+address.
+
+@item preference
+It contains load address placement suggestion for Multiboot2 modules

s/Multiboot2 modules/the boot loader./

Yes, will do.

Quoted 4 lines

doc/multiboot.texi Boot loader should follow it. @samp{0} means none, @samp{1} means · line 770

Quoted 2 lines
doc/multiboot.texi +2 -0
+Boot loader should follow it. @samp{0} means load modules not lower
+than min_addr, and not higher than max_addr, but no preference on either

s/,//g

Yes, will do.

Quoted 4 lines
Quoted 2 lines

+lower or higher address; @samp{1} means load modules at lowest possible

s/;/./

Yes, will do.

Quoted 3 lines
Quoted 1 line

+address but not lower than min_addr; @samp{2} means load modules at

s/;/./

Yes, will do.

Quoted 10 lines
Quoted 1 line

+highest possible address but not higher than max_addr.

After reading all threads related to this change somehow I got an impression that you want to use this tag to ask the booloader to load the modules above the kernel. Am I right? If this is true then we should have another value, 4, which says: please load modules above the kernel. ...and maybe 8 for below the kernel... Or vice versa would be better. Otherwise IMO you will be playing games with relocatable tag and this new tag to gain what you want. This will be not nice and maybe not very reliable.

Not really. My purpose is to load modules not in the lower address and it doesn't Matter whether it's loaded before or after kernel image.

I chose quirk-modules-after-kernel just because this quirk is supported in multiboot, and it seems naturally to bring it to multiboot2 as well.

Quoted 1 line

Daniel

#4 lore raw
Quoted 67 lines · Zide

Hi Daniel,

Thank you very much for your review! Comments inline:

Best Regards,
Zide

Quoted 7 lines

-----Original Message-----
From: Daniel Kiper <[email protected]>
Sent: Thursday, May 7, 2020 5:54 AM
To: Chen, Zide <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] multiboot2: Add module relocatable tag to support modules relocation

Quoted 8 lines
Quoted 3 lines · Zide Chen

Also change the name from "relocatable header tag" to "kernel relocatable tag" to make it less confusing. These two tags are independent from each other.

First of all, the commit message should say what the patch does and why. Just in a few words. You do not need to repeat everything from below. Though it have to be clear what happens without looking at the patch content.

Yes, will do.

Quoted 2 lines

Additionally, may I ask you to send new patch for Multiboo2 spec with "[MULTIBOOT2 SPEC PATCH]" subject prefix instead of normal "[PATCH]" one?

Yes, will do.

Quoted 6 lines
Quoted 6 lines
---
 doc/multiboot.texi | 51 +++++++++++++++++++++++++++++++++++++++++-----
 doc/multiboot2.h   | 11 ++++++++++
 2 files changed, 57 insertions(+), 5 deletions(-)
Quoted 14 lines

doc/multiboot.texi executable header. · line 359

Quoted 11 lines
doc/multiboot.texi +2 -1
index df8a0d056e76..bf0150dc86a0 100644
@@ -355,7 +355,8 @@ executable header.
 * Console header tags::
 * Module alignment tag::
 * EFI boot services tag::
-* Relocatable header tag::
+* Kernel relocatable tag::
+* Module relocatable tag::

IMO this is not "Module relocatable tag". It is rather "Module load preferences tag".

Sure, I can change the name. I chose this name because the contain of this new tag is almost identical to the relocatable header tag.

Quoted 6 lines
Quoted 6 lines
doc/multiboot.texi +0 -0
 @end menu
 
@@ -691,8 +692,8 @@ u32     | size = 8          |
 This tag indicates that payload supports starting without
 terminating boot services.
 
Quoted 6 lines

doc/multiboot.texi u32 | size = 8 | · line 696

Quoted 4 lines
doc/multiboot.texi +2 -2
-@node Relocatable header tag
-@subsection Relocatable header tag
+@node Kernel relocatable tag
+@subsection Kernel relocatable tag

I am OK with this change. However, it should be done in separate patch.

Quoted 2 lines

If this new tag is not named as "module relocatable tag", then I don't think it's needed to do this name changing any more, since now these two names are not confusing any more.

OK.

[...]

Quoted 11 lines
Quoted 10 lines

doc/multiboot.texi Boot loader should follow it. @samp{0} means none, @samp{1} means · line 773

Quoted 1 line
doc/multiboot.texi +1 -0
+highest possible address but not higher than max_addr.

After reading all threads related to this change somehow I got an impression that you want to use this tag to ask the booloader to load the modules above the kernel. Am I right? If this is true then we should have another value, 4, which says: please load modules above the kernel. ...and maybe 8 for below the kernel... Or vice versa would be better. Otherwise IMO you will be playing games with relocatable tag and this new tag to gain what you want. This will be not nice and maybe not very reliable.

Quoted 2 lines

Not really. My purpose is to load modules not in the lower address and it doesn't Matter whether it's loaded before or after kernel image.

Then you can ignore my comment above.

Daniel