From: Christoph Hellwig <hch@xxxxxx> If we need a NUMA crossing a mids a contiguous memory range we split the range at NUMA boundary so to produce two pmemX devices. We do not like 2 NUMA IDs at the same device. TODO: What happens with real type-12 NvDIMM the BIOS splits these ranges? Christoph I please need this patch for now. I have booting problems on some machines, when a contiguous pmem range crosses a NUMA boundary. Signed-off-by: Boaz Harrosh <boaz@xxxxxxxxxxxxx> --- arch/x86/kernel/e820.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c index 4bd525a..a098c74 100644 --- a/arch/x86/kernel/e820.c +++ b/arch/x86/kernel/e820.c @@ -346,7 +346,7 @@ int __init sanitize_e820_map(struct e820entry *biosmap, int max_nr_map, * continue building up new bios map based on this * information */ - if (current_type != last_type) { + if (current_type != last_type || current_type == E820_PRAM) { if (last_type != 0) { new_bios[new_bios_entry].size = change_point[chgidx]->addr - last_addr; -- 1.9.3 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html