Re: [PATCH] x86: fix init_memory_mapping over boundary v2
- Date: Sat, 28 Jun 2008 08:35:00 +0200
- From: Ingo Molnar <mingo@xxxxxxx>
- Subject: Re: [PATCH] x86: fix init_memory_mapping over boundary v2
* Yinghai Lu <yhlu.kernel@xxxxxxxxx> wrote: > some end boundary is only page alignment, instead of 2M alignment, so > call ker_phycial_mapping_init three times. then don't overmap above > the max_low_pfn applied to tip/x86/unify-setup, thanks Yinghai. > v2: make init_memory_mapping more solid: start could be any value > other than 0 very good idea! Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] x86: fix init_memory_mapping over boundary v2
- From: Ingo Molnar
- Re: [PATCH] x86: fix init_memory_mapping over boundary v2
- From: Yinghai Lu
- Re: [PATCH] x86: fix init_memory_mapping over boundary v2
- References:
- [PATCH 00/16] x86: merge setup_32/64.c
- From: Yinghai Lu
- [PATCH] x86: move fix mapping page table range early
- From: Yinghai Lu
- [PATCH] x86: fix init_memory_mapping over boundary
- From: Yinghai Lu
- [PATCH] x86: fix init_memory_mapping over boundary v2
- From: Yinghai Lu
- [PATCH 00/16] x86: merge setup_32/64.c
- Prev by Date: Re: [PATCH 0/3] Fix copy_user on x86_64
- Next by Date: Re: [PATCH] x86: early res print out alignment v2
- Previous by thread: [PATCH] x86: fix init_memory_mapping over boundary v2
- Next by thread: Re: [PATCH] x86: fix init_memory_mapping over boundary v2
- Index(es):