diff options
| author | Ingo Molnar <mingo@elte.hu> | 2008-02-21 11:04:11 +0100 | 
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-02-26 12:55:56 +0100 | 
| commit | 88f3aec7afd9ae3e6f6d221801996b69aad1e3a4 (patch) | |
| tree | 676a32c7bd248a15f2926bc6dcd03ace4971d442 /scripts/mod/empty.c | |
| parent | 3b57bc461fd5019aef4cfc77d4faf56ebe95449c (diff) | |
x86: fix spontaneous reboot with allyesconfig bzImage
recently the 64-bit allyesconfig bzImage kernel started spontaneously
rebooting during early bootup.
after a few fun hours spent with early init debugging, it turns out
that we've got this rather annoying limit on the size of the kernel
image:
      #define KERNEL_TEXT_SIZE  (40*1024*1024)
which limit my vmlinux just happened to pass:
       text           data       bss        dec       hex   filename
   29703744        4222751   8646224   42572719   2899baf   vmlinux
40 MB is 42572719 bytes, so my vmlinux was just 1.5% above this limit :-/
So it happily crashed right in head_64.S, which - as we all know - is
the most debuggable code in the whole architecture ;-)
So increase the limit to allow an up to 128MB kernel image to be mapped.
(should anyone be that crazy or lazy)
We have a full 4K of pagetable (level2_kernel_pgt) allocated for these
mappings already, so there's no RAM overhead and the limit was rather
pointless and arbitrary.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'scripts/mod/empty.c')
0 files changed, 0 insertions, 0 deletions
