Yes, the new API accept a "bool btrace" parameter. When, for example, you
write to printk(), you get the raw data (with timestamp), while when used
in TRACAME(), it is used with btrace==TRUE.


On Mon, Nov 9, 2015 at 8:56 AM, Barret Rhoden <[email protected]> wrote:

> On 2015-11-05 at 14:22 "'Davide Libenzi' via Akaros"
> <[email protected]> wrote:
> > Example:
> >
> > / $ cat /prof/kptrace
> > [      8.102085467]:cpu0: kern/drivers/dev/kprof.c(227)
> >         Backtrace:
> >         #01 [<0xffffffffc207233e>] in trace_printk
>
> Can we make trace_printk just do a print instead of a backtrace?  Then
> we can have something else for the backtrace?  I basically tried to
> make it just like ftrace's trace_printk(), where you can inject text
> into the trace: https://lwn.net/Articles/365835/. (grep trace_printk).
>
> Barret
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Akaros" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Akaros" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to