On Fri, 9 Jan 2009, Andi Kleen wrote:
>
> Universal noinline would also be a bad idea because of its
> costs (4.1% text size increase). Perhaps should make it
> a CONFIG option for debugging though.
That's _totally_ the wrong way.
If you can reproduce an issue on your machine, you generally don't care
about inline, because you can see the stack, do the whole "gdb vmlinux"
thing, and you generally have tools to help you decode things. Including
just recompiling the kernel with an added noinline.
But _users_ just get their oopses sent automatically. So it's not about
"debugging kernels", it's about _normal_ kernels. They are the ones that
need to be debuggable, and the ones that care most about things like the
symbolic EIP being as helpful as possible.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
