From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Song Liu <songliubraving@fb.com>
Cc: bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Peter Ziljstra <peterz@infradead.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>,
john fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>
Subject: Re: [PATCH v3 bpf-next 1/4] perf: expose get/put_callchain_entry()
Date: Sat, 27 Jun 2020 13:34:45 -0700 [thread overview]
Message-ID: <CAEf4BzY0CbYK=C_wxU8xw=jm8CSpHddfyi7ccPKe2gxJeN6gAA@mail.gmail.com> (raw)
In-Reply-To: <20200627002609.3222870-2-songliubraving@fb.com>
On Fri, Jun 26, 2020 at 5:26 PM Song Liu <songliubraving@fb.com> wrote:
>
> Sanitize and expose get/put_callchain_entry(). This would be used by bpf
> stack map.
>
> Suggested-by: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Song Liu <songliubraving@fb.com>
> ---
Acked-by: Andrii Nakryiko <andriin@fb.com>
> include/linux/perf_event.h | 2 ++
> kernel/events/callchain.c | 13 ++++++-------
> 2 files changed, 8 insertions(+), 7 deletions(-)
>
[...]
next prev parent reply other threads:[~2020-06-27 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 0:26 [PATCH v3 bpf-next 0/4] bpf: introduce bpf_get_task_stack() Song Liu
2020-06-27 0:26 ` [PATCH v3 bpf-next 1/4] perf: expose get/put_callchain_entry() Song Liu
2020-06-27 20:34 ` Andrii Nakryiko [this message]
2020-06-27 0:26 ` [PATCH v3 bpf-next 1/4] perf: expose get/put_chain_entry() Song Liu
2020-06-27 0:26 ` [PATCH v3 bpf-next 2/4] bpf: introduce helper bpf_get_task_stack() Song Liu
2020-06-27 20:35 ` Andrii Nakryiko
2020-06-27 0:26 ` [PATCH v3 bpf-next 3/4] bpf: allow %pB in bpf_seq_printf() and bpf_trace_printk() Song Liu
2020-06-27 0:26 ` [PATCH v3 bpf-next 4/4] selftests/bpf: add bpf_iter test with bpf_get_task_stack() Song Liu
2020-06-27 0:42 ` Yonghong Song
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='CAEf4BzY0CbYK=C_wxU8xw=jm8CSpHddfyi7ccPKe2gxJeN6gAA@mail.gmail.com' \
--to=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).