diff options
| author | Jacob Shin <jacob.shin@amd.com> | 2012-10-24 14:24:44 -0500 |
|---|---|---|
| committer | H. Peter Anvin <hpa@linux.intel.com> | 2012-10-24 13:37:04 -0700 |
| commit | 844ab6f993b1d32eb40512503d35ff6ad0c57030 (patch) | |
| tree | 59889d2391056d36307b4c5d587f1db6c7952d30 /fs/ramfs | |
| parent | 1f2ff682ac951ed82cc043cf140d2851084512df (diff) | |
x86, mm: Find_early_table_space based on ranges that are actually being mapped
Current logic finds enough space for direct mapping page tables from 0
to end. Instead, we only need to find enough space to cover mr[0].start
to mr[nr_range].end -- the range that is actually being mapped by
init_memory_mapping()
This is needed after 1bbbbe779aabe1f0768c2bf8f8c0a5583679b54a, to address
the panic reported here:
https://lkml.org/lkml/2012/10/20/160
https://lkml.org/lkml/2012/10/21/157
Signed-off-by: Jacob Shin <jacob.shin@amd.com>
Link: http://lkml.kernel.org/r/20121024195311.GB11779@jshin-Toonie
Tested-by: Tom Rini <trini@ti.com>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Diffstat (limited to 'fs/ramfs')
0 files changed, 0 insertions, 0 deletions