> This is a shame, but not a real problem in the context of my patch - you can't > usefully optimise something that's seemingly almost never used. It can be filed > in the cylindrical filing cabinet. I'll probably apply it anyway ... it looks like it will be useful when I get things like this working. The initial problem with kmemleak seems to be configuration related. I cut back from 4096 cpus on 1024 nodes to a more modest 32 cpus on 8 nodes, and my system boots. Still can't test your patch because although debugfs got configured and apparently built-in ok ... I can't see it in /proc/filesystems, so it won't mount. Thanks -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|