From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Song Liu <songliubraving@fb.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Kernel Team <Kernel-team@fb.com>, Netdev <netdev@vger.kernel.org>
Subject: Re: Pull patches from tip/perf/core to bpf-next
Date: Tue, 5 Feb 2019 19:36:02 -0800 [thread overview]
Message-ID: <20190206033600.6terh4xgozy5r3hs@ast-mbp> (raw)
In-Reply-To: <545C47EB-4D9A-46A5-892B-D4DDB88AFFDD@fb.com>
On Tue, Feb 05, 2019 at 10:47:06PM +0000, Song Liu wrote:
> Hi Alexei and Daniel,
>
> The following patches are required for BPF introspection in perf tools.
> Please pull them to bpf-next, so that we get all the dependencies in one
> tree.
>
> Thanks,
> Song
>
> (from 1/10 to 10/10)
> 76193a94522f perf, bpf: Introduce PERF_RECORD_KSYMBOL
> d764ac646491 tools headers uapi: Sync tools/include/uapi/linux/perf_event.h
> 6ee52e2a3fe4 perf, bpf: Introduce PERF_RECORD_BPF_EVENT
> df063c83aa2c tools headers uapi: Sync tools/include/uapi/linux/perf_event.h
> 9aa0bfa370b2 perf tools: Handle PERF_RECORD_KSYMBOL
> 45178a928a4b perf tools: Handle PERF_RECORD_BPF_EVENT
> 7b612e291a5a perf tools: Synthesize PERF_RECORD_* for loaded BPF programs
> a40b95bcd30c perf top: Synthesize BPF events for pre-existing loaded BPF programs
> 6934058d9fb6 bpf: Add module name [bpf] to ksymbols for bpf programs
> 811184fb6977 perf bpf: Fix synthesized PERF_RECORD_KSYMBOL/BPF_EVENT
yes. we can certainly do that.
Do you have bpf specific patches that depend on that ?
Since it's rc5 already. Are you planning to send them within next week?
next prev parent reply other threads:[~2019-02-06 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 22:47 Pull patches from tip/perf/core to bpf-next Song Liu
2019-02-06 3:36 ` Alexei Starovoitov [this message]
2019-02-06 3:44 ` Song Liu
2019-02-06 3:47 ` Alexei Starovoitov
2019-02-06 4:07 ` 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=20190206033600.6terh4xgozy5r3hs@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=Kernel-team@fb.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox