diff options
| author | Bob Picco <bob.picco@hp.com> | 2006-06-28 12:54:55 -0400 |
|---|---|---|
| committer | Tony Luck <tony.luck@intel.com> | 2006-08-03 10:12:30 -0700 |
| commit | 921eea1cdf6ce7f0db88e4579474a04b1fb0fe6d (patch) | |
| tree | 51a9099562dffa2276100f1bff429cc5dc2e4118 /kernel | |
| parent | 0a69ca91be2b36f99a48daacd1f12d9d49ecaf87 (diff) | |
| download | op-kernel-dev-921eea1cdf6ce7f0db88e4579474a04b1fb0fe6d.zip op-kernel-dev-921eea1cdf6ce7f0db88e4579474a04b1fb0fe6d.tar.gz | |
[IA64] align high endpoint of VIRTUAL_MEM_MAP
Assure that vmem_map's high endpoint is MAX_ORDER aligned. Not doing so violates
the buddy allocator algorithm. Also anyone using mem=XXX on boot line and
not aligned to MAX_ORDER requires this patch in order to satisfy buddy
allocator. vmem_map always starts at pfn 0. The potentially large MAX_ORDER
on ia64 (due to hugetlbfs) requires that the end of vmem_map be aligned
to MAX_ORDER_NR_PAGES.
This was boot tested for: FLATMEM, FLATMEM+VIRTUAL_MEM_MAP,
DISCONTIGMEM+VIRTUAL_MEM_MAP and SPARSEMEM.
Signed-off-by: Bob Picco <bob.picco@hp.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions
