> [...]>> There should be no extra function calls when this is configured on but >> tracing disabled. We try very hard to keep the speed of the tracer as >> close to a non tracing kernel as possible when tracing is disabled.>> Makes sense. But then we have even more code bloat because of the> tests that are inserted in all call sites of kmalloc.

Are you talking about the tests that implement checking whether amarker is active or not? Those checks are already efficient, and willget more so with the "immediate values" optimization in or near thetree.