Steven Rostedt wrote:
IIRC, only CALLER_ADDR0 is actually used (I've found that the others are mostly unreliable).
I seem to recall more use was made of __builtin_return_address(n) for 0 < n in the past compared to the current code. Likely for shallow frames the 0 < n calls were potentially returning invalid data which is why they currently appear to be commented out. Rather than lobbying to fix __builtin_return_address(), replacing it with a primitive which works in all cases seems an easier solution. That stub stack frame really does provide useful debug information. In the case of ARM I simply walked the stack. Worst case in that vintage of the code was four iterations so the overhead was in the noise. That same solution could easily be applied to other architectures.
It's been several years since I've worked on mips (I'd love to do it again, if someone sends me a box!, hint hint).
Concerning a MIPS board, if no freebies should arrive you might want to dig up a linux footprint friendly version of a Linksys WRT54GS. -john -- [EMAIL PROTECTED] - 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/
