Re: What's TRACE_IRQS_OFF_DEBUG for?

On Thu, 5 Nov 2015 23:24:22 -0800 Andy Lutomirski wrote: > The comment says: > > /* > * When dynamic function tracer is enabled it will add a breakpoint > * to all locations that it is about to modify, sync CPUs, update > * all the code, sync CPUs, then remove the breakpoints. In this time >

Re: What's TRACE_IRQS_OFF_DEBUG for?

On Thu, 5 Nov 2015 23:24:22 -0800 Andy Lutomirski wrote: > The comment says: > > /* > * When dynamic function tracer is enabled it will add a breakpoint > * to all locations that it is about to modify, sync CPUs, update > * all the code, sync CPUs, then remove the

What's TRACE_IRQS_OFF_DEBUG for?

The comment says: /* * When dynamic function tracer is enabled it will add a breakpoint * to all locations that it is about to modify, sync CPUs, update * all the code, sync CPUs, then remove the breakpoints. In this time * if lockdep is enabled, it might jump back into the debug handler *

What's TRACE_IRQS_OFF_DEBUG for?

The comment says: /* * When dynamic function tracer is enabled it will add a breakpoint * to all locations that it is about to modify, sync CPUs, update * all the code, sync CPUs, then remove the breakpoints. In this time * if lockdep is enabled, it might jump back into the debug handler *