On Wed, 10 Oct 2012, Yinghai Lu wrote: > on top of tip/x86/mm2, but please zap last patch in that branch. > > 1. use brk to mapping first PMD_SIZE range. > 2. top down to initialize page table range by range. > 3. get rid of calculate page table, and find_early_page_table. > 4. remove early_ioremap in page table accessing. > > v2: changes, update xen interface about pagetable_reserve, so not > use pgt_buf_* in xen code directly. > v3: use range top-down to initialize page table, so will not use > calculating/find early table anymore. > also reorder the patches sequence. > > could be found at: > > git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git > for-x86-mm > > later we could get rid of workaround about xen_mapping_pagetable_reserve, that > could kill another 50 lines codes. --- will do that later because x86/mm2 is > not updated to linus/master yet. If we do that now, will have merge conflicts.
I don't think you can change the x86 code without changing the xen code at the same time, otherwise you'll be really likely to break Xen. That is unless you don't change any of the pvops but I thought that it was one of the point of this series. > Yinghai Lu > > Yinghai Lu (7): > x86, mm: align start address to correct big page size > x86, mm: Use big page size for small memory range > x86, mm: Don't clear page table if next range is ram > x86, mm: only keep initial mapping for ram > x86, mm: Break down init_all_memory_mapping > x86, mm: setup page table from top-down > x86, mm: Remove early_memremap workaround for page table accessing > > arch/x86/include/asm/page_types.h | 1 + > arch/x86/include/asm/pgtable.h | 1 + > arch/x86/kernel/setup.c | 3 + > arch/x86/mm/init.c | 251 ++++++++++++------------------------ > arch/x86/mm/init_32.c | 18 +++- > arch/x86/mm/init_64.c | 100 ++++++--------- > 6 files changed, 144 insertions(+), 230 deletions(-) So you are missing the Xen patches entirely in this iteration of the series? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
