The 'addr' is used to request the memory with specific ranges but the
real loadable address come from the relocator.
Thus, print the final retrieved addresses (virtual and physical) for
initrd.
v2: append SOB
v3: fix wrong code base
Signed-off-by: Jeremy Szu
---
grub-core/loader/i386/linux.c
The 'addr' is used to request the memory with specific ranges but the
real loadable address come from the relocator.
Thus, print the final retrieved addresses (virtual and physical) for
initrd.
v2: append SOB
Signed-off-by: Jeremy Szu
---
grub-core/loader/i386/linux.c | 4 ++--
1 file changed
On Fri, Dec 16, 2022 at 1:33 PM Glenn Washburn
wrote:
>
> Signed-off-by: Glenn Washburn
> ---
> docs/grub-dev.texi | 191 +
> 1 file changed, 191 insertions(+)
>
> diff --git a/docs/grub-dev.texi b/docs/grub-dev.texi
> index f76fc658bf..8171e91c33
Hi Daniel,
On Tue, Dec 13, 2022 at 8:10 PM Daniel Kiper wrote:
>
> On Fri, Dec 09, 2022 at 12:07:49PM +0800, Jeremy Szu wrote:
> > From: Jeremy Su
> >
> > The 'addr' is used to request the memory with specific ranges but the
> > real loadable address come from
From: Jeremy Su
The 'addr' is used to request the memory with specific ranges but the
real loadable address come from the relocator.
Thus, print the final retrieved addresses (virtual and physical) for
initrd.
---
grub-core/loader/i386/linux.c | 4 ++--
1 file changed, 2 insertions(+), 2
In some recent EFI firwmare implmentation, the Loader-Data, Loader-Code
and Conventional memory regions (grub loader prefer to use) are located
under 1G (for example some HP platforms). Which causes there are only
~700MB on a 8G HP platform. (There are other 4G+ memories available above
Protocal 2.13 (Kernel 3.14) supports xloadflags to check the kernel
supported boot loader. It's also kernel recommended to use.
---
include/grub/i386/linux.h | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/include/grub/i386/linux.h
ignore some limitations (seems for some legacy
platforms) and allow to allocate memory above 4G (if supported).
Jeremy Su (1):
grub-core/kern/efi/mm.c fix warning message
Jeremy Szu (2):
include/grub/i386/linux.h support xloadflags
kern/efi/mm: introduce 'mmunlimited' for allocates on highe
From: Jeremy Su
When enable print_memory_map() for debugging, the warning message
presents because of the types. Fix it by adding the macros in
include/grub/efi/api.h.
---
grub-core/kern/efi/mm.c | 5 -
include/grub/efi/api.h | 2 ++
2 files changed, 6 insertions(+), 1 deletion(-)
diff
n 1G (or initrd_addr_max), then it
will get overflow, especially in x86_64 arch.
Therefore, add a check point to prevent it overflow as well as having a
debug log for complex story of initrd addresses.
Signed-off-by: Jeremy Szu
---
grub-core/loader/i386/linux.c | 13 +
1 file changed
n 1G (or initrd_addr_max), then it
will get overflow, especially in x86_64 arch.
Therefore, add a check point to prevent it overflow as well as having a
debug log for complex story of initrd addresses.
Signed-off-by: Jeremy Szu
---
grub-core/loader/i386/linux.c | 13 +
1 file changed
11 matches
Mail list logo
