On 11.07.2013, at 14:33, Benjamin Herrenschmidt wrote: > On Thu, 2013-07-11 at 15:12 +1000, Alexey Kardashevskiy wrote: >>>> Any debug code is prohibited? Ok, I'll remove. >>> >>> Debug code that requires code changes is prohibited, yes. >>> Debug code that is runtime switchable (pr_debug, trace points, etc) >>> are allowed. > > Bollox. > > $ grep DBG\( arch/powerpc/ -r | wc -l > 418 > > Also pr_devel is not runtime switchable in normal kernels either and > still an "official" kernel interface. > >> Is there any easy way to enable just this specific udbg_printf (not all of >> them at once)? Trace points do not work in real mode as we figured out. > > The cleaner way to do it is to use some kind of local macro that you > enable/disable by changing a #define at the top of the function, possibly > several. If you do that in a way that doesn't bitrot, that's acceptable, yes. Something that leaves cpp compile checks working while optimizing out the debug code. Alex -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
