On Thu, 3 Dec 2015 15:09:26 +0000 Will Deacon <[email protected]> wrote:
> Yeah, I think the comments on x86 and arm64 are out of date. They also > mention the freeing of __init sections -- is that still a concern? No we black list them, any section that we are not sure will be there when we expect it to has recordmcount.c nop out the calls to mcount and they are ignored. Remember the e1000e bug? This was the reproducer. Anyway, on my todo list is to allow init sections to be traced. To do so would mean that I need to add generic code that lets ftrace know to remove init sections at boot up. Right now (or at least the last time I checked, which was back in 2009), every arch had its own way of freeing init memory. If that has changed, or I can just place a hook where it happens (which is probably the easy part), I can allow init code to be traced too. -- Steve -- 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/
