On Fri, Dec 21, 2012 at 3:39 PM, Konrad Rzeszutek Wilk <[email protected]> wrote: > On Fri, Dec 21, 2012 at 02:44:39PM -0800, Yinghai Lu wrote: >> >> maybe we can change the subject of this patch to: >> >> Subject: [PATCH] x86, 64bit: Don't set max_pfn_mapped wrong on native boot >> path > > Or the inverse. > > Set max_pfn_mapped correctly on non-native boot path? > > But this patch is not actually touching max_pfn_mapped - it is vaddr_end?
No, it is 0 for native path > So maybe: > > Subject: For platforms to set max_pfn_mapped, take that under advisement when > blowing away __ka page entries. hard to understand. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
