On Mon, Dec 08, 2014 at 04:04:52PM +, Dave P Martin wrote:
> On Mon, Dec 08, 2014 at 03:42:10PM +, Steven Rostedt wrote:
> > On Fri, 5 Dec 2014 19:04:12 +
> > "Javi Merino" wrote:
>
> [...]
>
> > > +
> > > +DEFINE_PRINT_ARRAY(u8, unsigned int, "0x%x");
> > > +DEFINE_PRINT_ARRAY(u16,
On Mon, Dec 08, 2014 at 03:42:10PM +, Steven Rostedt wrote:
> On Fri, 5 Dec 2014 19:04:12 +
> "Javi Merino" wrote:
[...]
> > +
> > +DEFINE_PRINT_ARRAY(u8, unsigned int, "0x%x");
> > +DEFINE_PRINT_ARRAY(u16, unsigned int, "0x%x");
> > +DEFINE_PRINT_ARRAY(u32, unsigned int, "0x%x");
> > +
On Fri, 5 Dec 2014 19:04:12 +
"Javi Merino" wrote:
> +static const char *
> +ftrace_print_array_seq(struct trace_seq *p, const void *buf, int buf_len,
> +bool (*iterator)(struct trace_seq *p, const char *prefix,
> + const void **buf,
On Fri, Dec 05, 2014 at 07:04:12PM +, Javi Merino wrote:
> From: Dave Martin
>
> If a trace event contains an array, there is currently no standard
> way to format this for text output. Drivers are currently hacking
> around this by a) local hacks that use the trace_seq functionailty
> direc
From: Dave Martin
If a trace event contains an array, there is currently no standard
way to format this for text output. Drivers are currently hacking
around this by a) local hacks that use the trace_seq functionailty
directly, or b) just not printing that information. For fixed size
arrays, fo
5 matches
Mail list logo