Jan, I noticed yesterday that the DirectMap counts at the bottom of x86_64's /proc/meminfo are wrong on v3.5 and v3.6. For example, I happen to have booted this laptop with mem=700M to run a test, but /proc/meminfo shows
DirectMap4k: 4096 kB DirectMap2M: 18446744073709547520 kB Or if I boot with the full amount of physical memory, the DirectMap numbers do not add up to the full amount of physical memory, as they used to do on v3.4 and before. Whilst I've not yet tried reverting it, I strongly suspect your 20167d3421a0 "x86-64: Fix accounting in kernel_physical_mapping_init()". Either it was a complete misunderstanding, totally bogus, and should simply be reverted; or perhaps you really noticed something wrong in your code inspection, but didn't get the fix quite right? Hugh -- 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/