From: Yinghai Lu <yinghai@kernel.org>
To: Matt Fleming <matt.fleming@intel.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH 2/2] efilinux: set ext_ramdisk_* for huge initrd
Date: Tue, 17 Jun 2014 23:41:09 -0700 [thread overview]
Message-ID: <1403073669-6602-2-git-send-email-yinghai@kernel.org> (raw)
In-Reply-To: <1403073669-6602-1-git-send-email-yinghai@kernel.org>
We could load it high if it is more than 2G when kernel support
LOAD_ABOVE_4G.
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
---
loaders/bzimage/bzimage.c | 9 ++++++++-
loaders/bzimage/bzimage.h | 8 ++++++--
2 files changed, 14 insertions(+), 3 deletions(-)
Index: efilinux/loaders/bzimage/bzimage.c
===================================================================
--- efilinux.orig/loaders/bzimage/bzimage.c
+++ efilinux/loaders/bzimage/bzimage.c
@@ -130,7 +130,9 @@ static void parse_initrd(EFI_LOADED_IMAG
if (err != EFI_SUCCESS)
goto close_handles;
- if ((UINTN)addr > boot_params->hdr.ramdisk_max) {
+ if ((boot_params->hdr.version < 0x20c ||
+ !(boot_params->hdr.xloadflags & (1<<1))) &&
+ (UINTN)addr > boot_params->hdr.ramdisk_max) {
Print(L"ramdisk address is too high!\n");
efree(addr, size);
goto close_handles;
@@ -138,6 +140,11 @@ static void parse_initrd(EFI_LOADED_IMAG
boot_params->hdr.ramdisk_start = (UINT32)(UINTN)addr;
boot_params->hdr.ramdisk_len = (UINT32)size;
+ if (boot_params->hdr.version >= 0x20c &&
+ (boot_params->hdr.xloadflags & (1<<1))) {
+ boot_params->ext_ramdisk_image = (UINT64)(UINTN)addr >> 32;
+ boot_params->ext_ramdisk_size = size >> 32;
+ }
for (j = 0; j < nr_initrds; j++) {
struct initrd *rd = &initrds[j];
Index: efilinux/loaders/bzimage/bzimage.h
===================================================================
--- efilinux.orig/loaders/bzimage/bzimage.h
+++ efilinux/loaders/bzimage/bzimage.h
@@ -69,7 +69,8 @@ struct setup_header {
UINT32 ramdisk_max; /* Highest legal initrd address */
UINT32 kernel_alignment; /* Physical addr alignment required for kernel */
UINT8 relocatable_kernel; /* Whether kernel is relocatable or not */
- UINT8 _pad2[3];
+ UINT8 min_alignment;
+ UINT16 xloadflags;
UINT32 cmdline_size;
UINT32 hardware_subarch;
UINT64 hardware_subarch_data;
@@ -148,7 +149,10 @@ struct boot_params {
UINT8 hd1_info[16];
UINT8 sys_desc_table[0x10];
UINT8 olpc_ofw_header[0x10];
- UINT8 _pad4[128];
+ UINT32 ext_ramdisk_image;
+ UINT32 ext_ramdisk_size;
+ UINT32 ext_cmd_line_ptr;
+ UINT8 _pad4[116];
UINT8 edid_info[0x80];
struct efi_info efi_info;
UINT32 alt_mem_k;
next prev parent reply other threads:[~2014-06-18 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 6:41 [PATCH 1/2] efilinux: Allocate boot_params before parsing initrd Yinghai Lu
2014-06-18 6:41 ` Yinghai Lu [this message]
2014-06-25 20:47 ` [PATCH 2/2] efilinux: set ext_ramdisk_* for huge initrd Matt Fleming
2014-06-25 20:45 ` [PATCH 1/2] efilinux: Allocate boot_params before parsing initrd Matt Fleming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1403073669-6602-2-git-send-email-yinghai@kernel.org \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).