Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1179139 > unrolled thread

Re: [RFC PATCH v3 1/2] tracing: Add new trace type for bpf data output

Started byPeter Zijlstra <peterz@infradead.org>
First post2015-07-08 00:50 +0200
Last post2015-07-08 00:50 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [RFC PATCH v3 1/2] tracing: Add new trace type for bpf data  output Peter Zijlstra <peterz@infradead.org> - 2015-07-08 00:50 +0200

#1179139 — Re: [RFC PATCH v3 1/2] tracing: Add new trace type for bpf data output

FromPeter Zijlstra <peterz@infradead.org>
Date2015-07-08 00:50 +0200
SubjectRe: [RFC PATCH v3 1/2] tracing: Add new trace type for bpf data output
Message-ID<pJJQC-36d-29@gated-at.bofh.it>
On Tue, Jul 07, 2015 at 11:43:05AM +0000, He Kuang wrote:
> +FTRACE_ENTRY_REG(bpf, trace_bpf,
> +
> +	TRACE_BPF,
> +
> +	F_STRUCT(
> +		__field(long,	size)

I would suggest using either u32 or u64, not a variable size type like
long.

> +		__array(u64,	raw_data,	TRACE_BPF_MAX_ENTRY)
> +	),
> +
> +	F_printk("%ld: (%016llx, ...)", __entry->size, __entry->raw_data[0]),
> +
> +	FILTER_OTHER,
> +
> +	perf_ftrace_event_register
> +);
> -- 
> 1.8.5.2
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web