On 06/11/2013 03:53:43 PM, Scott Wood wrote:
On 06/08/2013 11:57:48 AM, Aneesh Kumar K.V wrote:
With the config shared I am not finding anything wrong, but I can't
test
these configs. Also can you confirm what you bisect this to
e2b3d202d1dba8f3546ed28224ce485bc50010be
powerpc: Switch 16GB and 16MB explicit hugepages to a different page
table format
or
cf9427b85e90bb1ff90e2397ff419691d983c68b "powerpc: New hugepage
directory format"
It's e2b3d202d1dba8f3546ed28224ce485bc50010be.
It turned out to be the change from "pmd_none" to
"pmd_none_or_clear_bad". Making that change triggers the "bad pmd"
messages even when applied to v3.9 -- so we had bad pmds all along,
undetected. Now I get to figure out why. :-(
So, for both pud and pgd we only call "or_clear_bad" when is_hugepd
returns false. Why is it OK to do it unconditionally for pmd?
-Scott
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href