Commit 028b7858 authored by Paul Jackson's avatar Paul Jackson Committed by Thomas Gleixner

x86 boot: extend some internal memory map arrays to handle larger EFI input

Extend internal boot time memory tables to allow for up to
three entries per node, which may be larger than the 128 E820MAX
entries handled by the legacy BIOS E820 interface.  The EFI
interface, if present, is capable of passing memory map
entries for these larger node counts.

This patch requires an earlier patch that rewrote code depending
on these array sizes from using E820MAX explicitly to size loops,
to instead using ARRAY_SIZE() of the applicable array.

Another patch following this one will provide the code to pick
up additional memory entries passed via the EFI interface from
the BIOS and insert them in the following, now enlarged, arrays.
Signed-off-by: default avatarPaul Jackson <pj@sgi.com>
Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
parent c3965bd1
...@@ -149,10 +149,10 @@ int __init sanitize_e820_map(struct e820entry *biosmap, int max_nr_map, ...@@ -149,10 +149,10 @@ int __init sanitize_e820_map(struct e820entry *biosmap, int max_nr_map,
struct e820entry *pbios; /* pointer to original bios entry */ struct e820entry *pbios; /* pointer to original bios entry */
unsigned long long addr; /* address for this change point */ unsigned long long addr; /* address for this change point */
}; };
static struct change_member change_point_list[2*E820MAX] __initdata; static struct change_member change_point_list[2*E820_X_MAX] __initdata;
static struct change_member *change_point[2*E820MAX] __initdata; static struct change_member *change_point[2*E820_X_MAX] __initdata;
static struct e820entry *overlap_list[E820MAX] __initdata; static struct e820entry *overlap_list[E820_X_MAX] __initdata;
static struct e820entry new_bios[E820MAX] __initdata; static struct e820entry new_bios[E820_X_MAX] __initdata;
struct change_member *change_tmp; struct change_member *change_tmp;
unsigned long current_type, last_type; unsigned long current_type, last_type;
unsigned long long last_addr; unsigned long long last_addr;
......
...@@ -2,6 +2,41 @@ ...@@ -2,6 +2,41 @@
#define __ASM_E820_H #define __ASM_E820_H
#define E820MAP 0x2d0 /* our map */ #define E820MAP 0x2d0 /* our map */
#define E820MAX 128 /* number of entries in E820MAP */ #define E820MAX 128 /* number of entries in E820MAP */
/*
* Legacy E820 BIOS limits us to 128 (E820MAX) nodes due to the
* constrained space in the zeropage. If we have more nodes than
* that, and if we've booted off EFI firmware, then the EFI tables
* passed us from the EFI firmware can list more nodes. Size our
* internal memory map tables to have room for these additional
* nodes, based on up to three entries per node for which the
* kernel was built: MAX_NUMNODES == (1 << CONFIG_NODES_SHIFT),
* plus E820MAX, allowing space for the possible duplicate E820
* entries that might need room in the same arrays, prior to the
* call to sanitize_e820_map() to remove duplicates. The allowance
* of three memory map entries per node is "enough" entries for
* the initial hardware platform motivating this mechanism to make
* use of additional EFI map entries. Future platforms may want
* to allow more than three entries per node or otherwise refine
* this size.
*/
/*
* Odd: 'make headers_check' complains about numa.h if I try
* to collapse the next two #ifdef lines to a single line:
* #if defined(__KERNEL__) && defined(CONFIG_EFI)
*/
#ifdef __KERNEL__
#ifdef CONFIG_EFI
#include <linux/numa.h>
#define E820_X_MAX (E820MAX + 3 * MAX_NUMNODES)
#else /* ! CONFIG_EFI */
#define E820_X_MAX E820MAX
#endif
#else /* ! __KERNEL__ */
#define E820_X_MAX E820MAX
#endif
#define E820NR 0x1e8 /* # entries in E820MAP */ #define E820NR 0x1e8 /* # entries in E820MAP */
#define E820_RAM 1 #define E820_RAM 1
...@@ -18,7 +53,7 @@ struct e820entry { ...@@ -18,7 +53,7 @@ struct e820entry {
struct e820map { struct e820map {
__u32 nr_map; __u32 nr_map;
struct e820entry map[E820MAX]; struct e820entry map[E820_X_MAX];
}; };
extern struct e820map e820; extern struct e820map e820;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment