Skip to contentSkip to conversation

arm64: booti: allow to place kernel image anywhere in physical memory

PATCH Superseded Masahiro Yamada 2 participants 3 messages Mar 8, 2017 – Mar 9, 2017

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 arm64: booti: allow to place kernel image anywhere in physical memory

At first, the ARM64 Linux booting requirement recommended that the kernel image be placed text_offset bytes from 2MB aligned base near the start of usable system RAM because memory below that base address was unusable at that time.

This requirement was relaxed by Linux commit a7f8de168ace ("arm64:
allow kernel Image to be loaded anywhere in physical memory"). Since then, the bit 3 of the flags field indicates the tolerance of the kernel physical placement. If this bit is set, the 2MB aligned base may be anywhere in physical memory. For details, see Documentation/arm64/booting.txt of Linux.

The booti command should be also relaxed. If the bit 3 is set, images->ep is respected, and the image is placed at the nearest bootable location. Otherwise, it is relocated to the start of the system RAM to keep the original behavior.

---

Changes in v2:
- Use le64_to_cpu() for correct endian-ness
- Check the bit 3

 cmd/booti.c | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)
cmd/booti.c +14 -4
index bff87a8..8f3507d 100644
@@ -11,6 +11,8 @@
 #include <image.h>
 #include <lmb.h>
 #include <mapmem.h>
+#include <linux/kernel.h>
+#include <linux/sizes.h>
 
 DECLARE_GLOBAL_DATA_PTR;
 
@@ -20,7 +22,7 @@ struct Image_header {
 	uint32_t	code1;		/* Executable code */
 	uint64_t	text_offset;	/* Image load offset, LE */
 	uint64_t	image_size;	/* Effective Image size, LE */
-	uint64_t	res1;		/* reserved */
+	uint64_t	flags;		/* Kernel flags, LE */
 	uint64_t	res2;		/* reserved */
 	uint64_t	res3;		/* reserved */
 	uint64_t	res4;		/* reserved */
@@ -51,10 +53,18 @@ static int booti_setup(bootm_headers_t *images)
 	}
 
 	/*
-	 * If we are not at the correct run-time location, set the new
-	 * correct location and then move the image there.
+	 * If bit 3 of the flags field is set, the 2MB aligned base of the
+	 * kernel image can be anywhere in physical memory, so respect
+	 * images->ep.  Otherwise, relocate the image to the base of RAM
+	 * since memory below it is not accessible via the linear mapping.
 	 */
-	dst = gd->bd->bi_dram[0].start + le64_to_cpu(ih->text_offset);
+	if (le64_to_cpu(ih->flags) & BIT(3))
+		dst = images->ep - le64_to_cpu(ih->text_offset);
+	else
+		dst = gd->bd->bi_dram[0].start;
+
+	dst = ALIGN(dst, SZ_2M);
+	dst += le64_to_cpu(ih->text_offset);
 
 	unmap_sysmem(ih);
 
Signature · 1 line
2.7.4
#1 lore raw

PATCH v2 1/1 arm64: booti: allow to place kernel image anywhere in physical memory

Quoted 53 lines · Masahiro Yamada

At first, the ARM64 Linux booting requirement recommended that the kernel image be placed text_offset bytes from 2MB aligned base near the start of usable system RAM because memory below that base address was unusable at that time.

This requirement was relaxed by Linux commit a7f8de168ace ("arm64:
allow kernel Image to be loaded anywhere in physical memory"). Since then, the bit 3 of the flags field indicates the tolerance of the kernel physical placement. If this bit is set, the 2MB aligned base may be anywhere in physical memory. For details, see Documentation/arm64/booting.txt of Linux.

The booti command should be also relaxed. If the bit 3 is set, images->ep is respected, and the image is placed at the nearest bootable location. Otherwise, it is relocated to the start of the system RAM to keep the original behavior.

---

Changes in v2:
- Use le64_to_cpu() for correct endian-ness
- Check the bit 3

 cmd/booti.c | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)
cmd/booti.c +3 -1
index bff87a8..8f3507d 100644
@@ -11,6 +11,8 @@
 #include <image.h>
 #include <lmb.h>
 #include <mapmem.h>
+#include <linux/kernel.h>
+#include <linux/sizes.h>
 
 DECLARE_GLOBAL_DATA_PTR;
 
@@ -20,7 +22,7 @@ struct Image_header {
 	uint32_t	code1;		/* Executable code */
 	uint64_t	text_offset;	/* Image load offset, LE */
 	uint64_t	image_size;	/* Effective Image size, LE */
-	uint64_t	res1;		/* reserved */
+	uint64_t	flags;		/* Kernel flags, LE */
 	uint64_t	res2;		/* reserved */
 	uint64_t	res3;		/* reserved */
 	uint64_t	res4;		/* reserved */
@@ -51,10 +53,18 @@ static int booti_setup(bootm_headers_t *images)
 	}
 
 	/*

cmd/booti.c static int booti_setup(bootm_headers_t *images) · line 62

Quoted 10 lines
cmd/booti.c +6 -3
-	 * If we are not at the correct run-time location, set the new
-	 * correct location and then move the image there.
+	 * If bit 3 of the flags field is set, the 2MB aligned base of the
+	 * kernel image can be anywhere in physical memory, so respect
+	 * images->ep.  Otherwise, relocate the image to the base of RAM
+	 * since memory below it is not accessible via the linear mapping.
 	 */
-	dst = gd->bd->bi_dram[0].start + le64_to_cpu(ih->text_offset);
+	if (le64_to_cpu(ih->flags) & BIT(3))
+		dst = images->ep - le64_to_cpu(ih->text_offset);

I take it this is a pre-correction for the ALIGN() below?

cmd/booti.c static int booti_setup(bootm_headers_t *images) · line 67

Quoted 5 lines
cmd/booti.c +5 -0
+	else
+		dst = gd->bd->bi_dram[0].start;
+
+	dst = ALIGN(dst, SZ_2M);
+	dst += le64_to_cpu(ih->text_offset);

There's one last wrinkle to take care of here, if we want to boot a kernel older than commit a2c1d73b94ed49f5 (i.e. v3.16). Until then, the text_offset was of unknown endianness.

As mentiond in the Linux documentation, you can detect this based on the image_size field, e.g.

	uint64_t text_offset;

	/*
	 * Prior to Linux commit a2c1d73b94ed49f5, the text_offset field
	 * is of unknown endianness. In these cases, the image_size
	 * field is zero, and we can assume a fixed value of 0x80000.
	 */
	if (le64_to_cpu(ih->image_size) == 0)
		text_offset = 0x80000;
	else
		text_offset = (le64_to_cpu(ih->text_offset));

... then you can reuse that text_offset value for both cases above.

Otherwise, this looks fine to me.

Thanks,
Mark.

#2 lore raw

PATCH v2 1/1 arm64: booti: allow to place kernel image anywhere in physical memory

Hi Mark,

2017-03-09 1:05 GMT+09:00 Mark Rutland <[email protected]>:

Quoted 13 lines

cmd/booti.c static int booti_setup(bootm_headers_t *images) · line 62

Quoted 12 lines
      /*
cmd/booti.c +6 -3
-      * If we are not at the correct run-time location, set the new
-      * correct location and then move the image there.
+      * If bit 3 of the flags field is set, the 2MB aligned base of the
+      * kernel image can be anywhere in physical memory, so respect
+      * images->ep.  Otherwise, relocate the image to the base of RAM
+      * since memory below it is not accessible via the linear mapping.
       */
-     dst = gd->bd->bi_dram[0].start + le64_to_cpu(ih->text_offset);
+     if (le64_to_cpu(ih->flags) & BIT(3))
+             dst = images->ep - le64_to_cpu(ih->text_offset);
Quoted 1 line

I take it this is a pre-correction for the ALIGN() below?

Without this, the image would be always relocated
even if images->ep is already bootable location.

Unnecessary relocation should be avoided.

Quoted 19 lines

There's one last wrinkle to take care of here, if we want to boot a kernel older than commit a2c1d73b94ed49f5 (i.e. v3.16). Until then, the text_offset was of unknown endianness.

As mentiond in the Linux documentation, you can detect this based on the image_size field, e.g.

        uint64_t text_offset;

        /*
         * Prior to Linux commit a2c1d73b94ed49f5, the text_offset field
         * is of unknown endianness. In these cases, the image_size
         * field is zero, and we can assume a fixed value of 0x80000.
         */
        if (le64_to_cpu(ih->image_size) == 0)
                text_offset = 0x80000;
        else
                text_offset = (le64_to_cpu(ih->text_offset));
Quoted 2 lines

... then you can reuse that text_offset value for both cases above.

Thanks. I will fix this too.

Signature · 2 lines
Best Regards
Masahiro Yamada