Re: [RFC PATCH v2 1/3] tracing: Show real address for trace event arguments

2020-10-15 Thread Masami Hiramatsu
On Thu, 15 Oct 2020 09:09:55 -0400 Steven Rostedt wrote: > On Thu, 15 Oct 2020 18:00:08 +0900 > Masami Hiramatsu wrote: > > > +#define STATIC_FMT_BUF_SIZE128 > > +static char static_fmt_buf[STATIC_FMT_BUF_SIZE]; > > + > > +const char *trace_event_format(struct trace_iterator *iter, cons

Re: [RFC PATCH v2 1/3] tracing: Show real address for trace event arguments

2020-10-15 Thread Steven Rostedt
On Thu, 15 Oct 2020 18:00:08 +0900 Masami Hiramatsu wrote: > +#define STATIC_FMT_BUF_SIZE 128 > +static char static_fmt_buf[STATIC_FMT_BUF_SIZE]; > + > +const char *trace_event_format(struct trace_iterator *iter, const char *fmt) > +{ > + const char *p, *new_fmt; > + char *q; > + > +

[RFC PATCH v2 1/3] tracing: Show real address for trace event arguments

2020-10-15 Thread Masami Hiramatsu
To help debugging kernel, show real address for trace event arguments in tracefs/trace{,pipe} instead of hashed pointer value. Since ftrace human-readable format uses vsprintf(), all %p are translated to hash values instead of pointer address. However, when debugging the kernel, raw address value