From: Peter Zijlstra <peterz@infradead.org>
To: Song Liu <songliubraving@fb.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH v5 perf, bpf-next 1/7] perf, bpf: Introduce PERF_RECORD_KSYMBOL
Date: Tue, 8 Jan 2019 20:43:43 +0100 [thread overview]
Message-ID: <20190108194343.GE1900@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <A7A11A44-FDF0-4FB5-98B6-3E47A35E7120@fb.com>
On Tue, Jan 08, 2019 at 06:56:19PM +0000, Song Liu wrote:
> I don't think we need u64 length. 32 bit should be more than enough.
>
> How about we revise it as:
Yep, works. Although I would not introduce types we're not yet
generating. We can add those easily enough when needed.
next prev parent reply other threads:[~2019-01-08 19:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 18:28 [PATCH v5 perf, bpf-next 0/7] reveal invisible bpf programs Song Liu
2018-12-20 18:28 ` [PATCH v5 perf, bpf-next 1/7] perf, bpf: Introduce PERF_RECORD_KSYMBOL Song Liu
2019-01-08 18:31 ` Peter Zijlstra
2019-01-08 18:56 ` Song Liu
2019-01-08 19:43 ` Peter Zijlstra [this message]
2018-12-20 18:28 ` [PATCH v5 perf, bpf-next 2/7] sync tools/include/uapi/linux/perf_event.h Song Liu
2018-12-20 18:29 ` [PATCH v5 perf, bpf-next 3/7] perf, bpf: introduce PERF_RECORD_BPF_EVENT Song Liu
2019-01-08 18:41 ` Peter Zijlstra
2019-01-08 19:10 ` Song Liu
2019-01-08 19:43 ` Peter Zijlstra
2019-01-08 23:54 ` Song Liu
2019-01-09 10:18 ` Peter Zijlstra
2019-01-09 11:32 ` Song Liu
2019-01-09 12:59 ` Peter Zijlstra
2019-01-09 16:04 ` Song Liu
2019-01-08 20:16 ` Arnaldo Carvalho de Melo
2019-01-08 23:37 ` Song Liu
2019-01-08 20:56 ` Alexei Starovoitov
2019-01-08 19:59 ` Peter Zijlstra
2019-01-08 20:29 ` Peter Zijlstra
2019-01-08 20:45 ` Alexei Starovoitov
2019-01-09 12:41 ` Peter Zijlstra
2019-01-09 15:51 ` Song Liu
2018-12-20 18:29 ` [PATCH v5 perf, bpf-next 4/7] sync tools/include/uapi/linux/perf_event.h Song Liu
2018-12-20 18:29 ` [PATCH v5 perf, bpf-next 5/7] perf util: handle PERF_RECORD_KSYMBOL Song Liu
2018-12-20 18:29 ` [PATCH v5 perf, bpf-next 6/7] perf util: handle PERF_RECORD_BPF_EVENT Song Liu
2018-12-20 18:29 ` [PATCH v5 perf, bpf-next 7/7] perf tools: synthesize PERF_RECORD_* for loaded BPF programs Song Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190108194343.GE1900@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Kernel-team@fb.com \
--cc=acme@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.