On Mon, Dec 14, 2015 at 10:39:19AM +, Wang Nan wrote:
SNIP
> # cat /sys/kernel/debug/tracing/trace | grep usleep
>usleep-405 [004] d... 2745423.547822: : 101
>usleep-655 [006] d... 2745434.122814: : 102
>usleep-904 [006] d... 2745439.916264: : 103
>
On Wed, Dec 16, 2015 at 10:02:28AM +0800, Wangnan (F) wrote:
>
>
> On 2015/12/15 21:42, Jiri Olsa wrote:
> >On Mon, Dec 14, 2015 at 10:39:19AM +, Wang Nan wrote:
> >>This patch introduce a new syntax to perf event parser:
> >>
> >> # perf record -e
> >> './test_bpf_map_3.c/maps:channel.valu
On 2015/12/15 21:42, Jiri Olsa wrote:
On Mon, Dec 14, 2015 at 10:39:19AM +, Wang Nan wrote:
This patch introduce a new syntax to perf event parser:
# perf record -e './test_bpf_map_3.c/maps:channel.value[0,1,2,3...5]=101/'
usleep 2
why 3 dots? I'd think the standard is 2 ?
The stand
On Mon, Dec 14, 2015 at 10:39:19AM +, Wang Nan wrote:
> This patch introduce a new syntax to perf event parser:
>
> # perf record -e './test_bpf_map_3.c/maps:channel.value[0,1,2,3...5]=101/'
> usleep 2
why 3 dots? I'd think the standard is 2 ? just curious
[0,1,2,3..5]
3 made me think the
This patch introduce a new syntax to perf event parser:
# perf record -e './test_bpf_map_3.c/maps:channel.value[0,1,2,3...5]=101/'
usleep 2
By utilizing the basic facilities in bpf-loader.c which allow setting
different slots in a BPF map separately, the newly introduced syntax
allows perf to c
5 matches
Mail list logo
