Using Dtrace for Performance Evaluation

[David Christensen]

> > After building dtrace into the kernel and loading the dtraceall
> > kernel module, when I load my bxe kernel module and run "dtrace -l"
> > to list all supported probes I notice that many functions have an
> > entry probe but no exit probe.  This effectively prevents me from
> > calculating timestamps on "fbt:if_bxe::return" probes.  Why am I
> > seeing this behavior?
> 
> Tail call optimization could do that to you:
> http://en.wikipedia.org/wiki/Tail_call

How to disable tail call optimization when building my driver?

Dave