From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: acme@kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, a.p.zijlstra@chello.nl, mingo@kernel.org,
mark.rutland@arm.com, namhyung@kernel.org,
alexander.shishkin@linux.intel.com, mpetlan@redhat.com,
songliubraving@fb.com, irogers@google.com, eranian@google.com,
abudankov@huawei.com, ak@linux.intel.com,
adrian.hunter@intel.com
Subject: Re: [PATCHv7 bpf-next 0/3] perf: Add mmap2 build id support
Date: Fri, 15 Jan 2021 03:50:08 +0000 [thread overview]
Message-ID: <161068260889.10644.18398465813919990190.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210114134044.1418404-1-jolsa@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Thu, 14 Jan 2021 14:40:41 +0100 you wrote:
> hi,
> adding the support to have buildid stored in mmap2 event,
> so we can bypass the final perf record hunt on build ids.
>
> This patchset allows perf to record build ID in mmap2 event,
> and adds perf tooling to store/download binaries to .debug
> cache based on these build IDs.
>
> [...]
Here is the summary with links:
- [bpf-next,1/3] bpf: Move stack_map_get_build_id into lib
https://git.kernel.org/bpf/bpf-next/c/bd7525dacd7e
- [bpf-next,2/3] bpf: Add size arg to build_id_parse function
https://git.kernel.org/bpf/bpf-next/c/921f88fc8919
- [bpf-next,3/3] perf: Add build id data in mmap2 event
https://git.kernel.org/bpf/bpf-next/c/88a16a130933
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-01-15 3:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 13:40 [PATCHv7 bpf-next 0/3] perf: Add mmap2 build id support Jiri Olsa
2021-01-14 13:40 ` [PATCH bpf-next 1/3] bpf: Move stack_map_get_build_id into lib Jiri Olsa
2021-01-14 13:40 ` [PATCH bpf-next 2/3] bpf: Add size arg to build_id_parse function Jiri Olsa
2021-01-14 18:56 ` Yonghong Song
2021-01-14 20:01 ` Jiri Olsa
2021-01-14 21:05 ` Yonghong Song
2021-01-14 22:02 ` Jiri Olsa
2021-01-14 23:43 ` Yonghong Song
2021-01-15 3:47 ` Alexei Starovoitov
2021-01-26 20:52 ` Jiri Olsa
2021-01-26 21:00 ` Yonghong Song
2021-01-14 13:40 ` [PATCH bpf-next 3/3] perf: Add build id data in mmap2 event Jiri Olsa
2021-01-15 3:50 ` patchwork-bot+netdevbpf [this message]
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=161068260889.10644.18398465813919990190.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=abudankov@huawei.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@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