[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQWrPtEe3tkJjgOzyJJPPzX=AtMYgR4c91pDHL3q3ZLLKQ@mail.gmail.com>
Date: Wed, 27 Aug 2014 10:13:22 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Matt Fleming <matt@...sole-pimps.org>
Cc: Matt Fleming <matt.fleming@...el.com>,
"H. Peter Anvin" <hpa@...or.com>,
Mantas Mikulėnas <grawity@...il.com>,
Anders Darander <anders@...rgestorm.se>,
linux-efi@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Harald Hoyer <harald@...hat.com>
Subject: Re: [PATCH] x86: only load initrd above 4g on second try
On Wed, Aug 27, 2014 at 3:59 AM, Matt Fleming <matt@...sole-pimps.org> wrote:
> On Tue, 26 Aug, at 02:45:44PM, Yinghai Lu wrote:
> The reason I suggested introducing some kind of kernel parameter to
> allow loading above 4G is because if Mantas loads a 5GB initrd with your
> patch, his machine is still going to hang, with no indication of why it
> hung.
>
> At least with a kernel paramter, by default we can try to load under 4G,
> and if that fails because the file is too big we can print something
> along the lines of,
>
> "initramfs file too large: try booting with efi=file-max"
>
> No, it's not ideal, but I think it's a worthwhile compromise because
> you're only going to run into this issue when loading a huge initramfs
> with the EFI boot stub.
I would like to avoid adding more kernel parameter.
How about adding more info print out like:
"Try to load initrd file to higher address..."
Thanks
Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists